hokiewalrus
Registered User.
- Local time
- Today, 14:25
- Joined
- Jan 19, 2009
- Messages
- 50
Hello all. I have a new project to build and it's significantly bigger than my other ones. It's replacing an old VB program so we were thinking of developing in the new VB.net environment, but I'm finding making the switch from VBA to full VB a lot tougher than I had anticipated. So it's gotten me thinking about trying in Access, but I was wondering if I was barking up the wrong tree.
The program is going to have it's own database (currently about 800MB from 5 years of use, though there will be no migration, new one will only be about 12 tables, though many many rows) and will have to access a separate SQL database very frequently. There will be about 40 users with roughly 20 using the program at any given time.
My options seem to be:
VB.net front end with MSSQL back end
Access front end with MSSQL back end
Access front and back end
I'm very concerned about Access's ability to handle that many concurrent users, but obviously it's the environment I'd prefer to use if I can.
Any advice would be greatly appreciated.
The program is going to have it's own database (currently about 800MB from 5 years of use, though there will be no migration, new one will only be about 12 tables, though many many rows) and will have to access a separate SQL database very frequently. There will be about 40 users with roughly 20 using the program at any given time.
My options seem to be:
VB.net front end with MSSQL back end
Access front end with MSSQL back end
Access front and back end
I'm very concerned about Access's ability to handle that many concurrent users, but obviously it's the environment I'd prefer to use if I can.
Any advice would be greatly appreciated.