Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Migrating MS Access to .NET

Posted on 2004-10-20
3
Medium Priority
?
143 Views
Last Modified: 2010-04-24
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,

David
0
Comment
Question by:David Smithstein
3 Comments
 
LVL 19

Accepted Solution

by:
arif_eqbal earned 2000 total points
ID: 12366757
Well I am not an authority on it though but I feel .NET will take much more memory and will be slower.

Also it will not be very easy converting all your 800 forms to VB.NET

But I'd still say go for it, memory these days is very cheap so you can have more of it
Processors are pretty fast these days and you won't notice a performance lag.

And at the expense of all these you can get a load of Features your forms can be more user friendly you can offer rich features.

For you to Decide.......


0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains how to create and use a custom WaterMark textbox class.  The custom WaterMark textbox class allows you to set the WaterMark Background Color and WaterMark text at design time.   IMAGE OF WATERMARKS STEPS Create VB …
Since .Net 2.0, Visual Basic has made it easy to create a splash screen and set it via the "Splash Screen" drop down in the Project Properties.  A splash screen set in this manner is automatically created, displayed and closed by the framework itsel…
Video by: ITPro.TV
In this episode Don builds upon the troubleshooting techniques by demonstrating how to properly monitor a vSphere deployment to detect problems before they occur. He begins the show using tools found within the vSphere suite as ends the show demonst…
Integration Management Part 2

916 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question