Migrating MS Access to .NET
Posted on 2004-10-20
After three years my MS Access 2002 application has grown to roughly 150 tables, 2000 queries, 800 forms, and about 150 reports. All relationships are handled at the query level (i.e. there are no linked tables) all functionality is via VBA coding with error trapping. (i.e. no macros) The application deploys as a .mde front end and a 2002 .mdb back end in a replicated data set using a hub database set at the maximum priority to help manage replication conflicts.
While Access has been a great platform for the "development" phase of the application, I am looking for ways to make improvements to what I suspect are inherently MS Access issues. I am wondering what options .NET would provide me and if the improvements would be worth the effort to migrate the application into a newer technology.
Here are my concerns/questions:
Memory useage: During use the application seems to require 40-50 MB of memory depending on how many forms are open. Is .NET inherently more or less of a memory user compared to MS Access?
Speed: While the .mde does speed the application up, and since all processing is done on the local drive, performance is good in most areas, but some areas could run a little faster. Does .NET inherently run faster
Replication: For the type of work the application does, a replicated topology works well and we like the remote and disconnected capability it offers. Do we have to sacrafice this if we move into SQL/.NET technologies?
And finally...how hard is it going to be to convert my monstrosity of a front end user interface into a .NET interface?
Thanks in advance,