Solved

Migrating MS Access to .NET

Posted on 2004-10-20
3
140 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 19

Accepted Solution

by:
arif_eqbal earned 500 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

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

If you're writing a .NET application to connect to an Access .mdb database and use pre-existing queries that require parameters, you've come to the right place! Let's say the pre-existing query(qryCust) in Access takes a Date as a parameter and l…
Parsing a CSV file is a task that we are confronted with regularly, and although there are a vast number of means to do this, as a newbie, the field can be confusing and the tools can seem complex. A simple solution to parsing a customized CSV fi…
In this video, viewers will be given step by step instructions on adjusting mouse, pointer and cursor visibility in Microsoft Windows 10. The video seeks to educate those who are struggling with the new Windows 10 Graphical User Interface. Change Cu…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Suggested Courses

627 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