asked on

Access VS MS.Net

Hi evereyone.
I am looking at what Access has to offer in terms of VBA functionality compared with Microsoft.NET backend. Any Ideas on the way forward here because up to now I have been very comfortable with MS Access but with the advent of 2007 there are quite a few changes that I have to make to a lot of the databases that we have already written. I am seriouly thinking of going the Microsoft.net route but the question then is what Front End. Your thoughts will be appreciated

SOLUTION

peter57r

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Scott McDaniel (EE MVE )

As pete said, the learning curve for these languages can be steep, especially if you're a "drag and drop" Access programmer, or someone who doesn't have a lot of OO experience.

I've had little trouble with Access in fairly large multi-user environments, but then I'm running my apps in full unbound mode so I avoid most of the performance troubles so often seen. If you have a wide user-base - especially if those users may or may not have Access 2007 installed - then the answer would be (to me, at least) to move to the .NET platform ... if this is a small workgroup on the same LAN, then Access will handle it easily.

caandal

ASKER

Thanks guys for the comments. I regard Access as the front-end - VBA sitting behind Access to all the nice things and then the Tables as the back end Currently depending on the application I stay with Access as the data holder in a small environment or use SQL as the back end in larger environments or with lots of data. I am very comfortable using VBA and must say that I don't use drag and drop or the wizards in Access very often.

ASKER CERTIFIED SOLUTION

Scott McDaniel (EE MVE )

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial