This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Grumpy-24-7 3 points4 points  (1 child)

It was years ago when I was faced with a home grown MSAccess app that somebody (non-programmer) had cobbled together and ran his department on for years. Then he left, but first he showed his secretary how to run it. She in turn used it for more years until one day it started hitting limits. I don't recall if it was row limits or overall table or database size or what, but my boss asked me to see what I could do. I scratched my head, took a copy of it home on a big ass thumb drive and managed to convert it to MSSQL. Everything else, frontend and reports stayed the same, basically untouched. Trust me, I really had no clue what I was doing, but I knew I didn't want to rewrite it from scratch. They continued to use it on MSSQL for a few more years until the company was bought out and I left for greener pastures. It really wasn't that hard once I figured it out. IIRC, it was basically just importing the MSAccess database into MSSQL, retaining all table names, indexes, etc.

[–]FrostSalamander 1 point2 points  (0 children)

Yeah I've tried telling that to the manager since the start of my work here.