QUOTE(baavgai @ 23 Nov, 2007 - 08:23 AM)
Do not use Access! Seriously, Access is great for just you, or a single user. It's not good for more than that, it's simply won't work.
Actually, it does work - had an 8 user Access application that worked quite well. It was split into an Access front end and an Access back end (then I converted the back end over to using a mySQL server)
QUOTE(baavgai @ 23 Nov, 2007 - 08:23 AM)
"Access database on server" is misleading. If it's a file on a server, it's still just an Access file.
Unless using SQL Server to serve up the Access records it is very true, the back end (and hopefully he has a front-end/back-end set up) is just a data file being served by a file server.
QUOTE(baavgai @ 23 Nov, 2007 - 08:23 AM)
Now, if the front end is actually VB, then you're in luck. Your option is to change the datasource to something that can play nice with many people, like SQL Server. If it's new VB.NET, you should be able to create a SQL Server Express instance for your project.
You're actually legally allowed to use SQL Express in your code, so no worries. It has size limits, but they're something like 5GB. Since you're normal Access file starts to circle the drain at far smaller than that, it's probably not an issue.
Hope this helps.
Now, answer the original question...
It sound like you have not set up your access application correctly. When using with multiple users you need to have either
1) back-end / front-end where each user has their own copy of the front-end (the application) and the back-end is located on the file server. With this you can then have the application (front-end) be an .mde so that the users do not foul things up.
2) the application/data is in a single .mdb file that has been set up for shared use. Please note that if the first user to sign in does not sign in for shared use that will then lock it out for all others
This post has been edited by kwikone: 24 Nov, 2007 - 10:55 AM
23 Nov, 2007 - 02:26 AM
| 