Help Please

[JonyBravo]

My access VB applications use to be built in access 97 but recently the company updated the software and is using now access 2003. My only problem so far is: my applications built in access 97 are able to be opened by over 40 users at the same time and but the ones built in access 2003 only allow me one each time. I'm sure is some setting that need to be change but I couldn’t find anything. Is there anyone that could help me please as a matter of urgency because I've got few projects ready to be launched but are waiting to solve this problem?

Thanks in advance

JonyBravo

 

[boblarson]

My access VB applications use to be built in access 97 but recently the company updated the software and is using now access 2003. My only problem so far is: my applications built in access 97 are able to be opened by over 40 users at the same time and but the ones built in access 2003 only allow me one each time. I'm sure is some setting that need to be change but I couldn’t find anything. Is there anyone that could help me please as a matter of urgency because I've got few projects ready to be launched but are waiting to solve this problem?

Thanks in advance

JonyBravo

The possibility exists that their initial user setting is to open exclusive, which would lock everyone out. I highly (and I mean HIGHLY suggest that you give your users their OWN copy of the front-end and have the backend with data on your server. Having 40 people accessing the same mdb file is just flirting with disaster. If you look in the sample database section here on the forum you will find a post of mine with an auto update enabling utility which, once you distribute your applications to your users one-time, means you won't have to ever send them a new version of the frontend after working on it. You just change the version numbers and it does the work for you.

But, anyway - you should be using a frontend/backend setup for your multi user databases and each user should have their own copy of the frontend. It is much more efficient and is much less prone to corruption issues.

 

[JonyBravo]

Hi boblarson
Thansk for your help. My first application few years ago I've done like you said, back end on one side and gave the each member a copy of the front end but I had a problem that I dint find out how to resolve. I had to manually link each front end application to the back end. On the biggining was only for the use of about 10 staff was ok but one year after the staff were about 40 people. Could you please send me the link of your post about auto update enabling utility?

Thansk again

 

[boblarson]

Hi boblarson
Thansk for your help. My first application few years ago I've done like you said, back end on one side and gave the each member a copy of the front end but I had a problem that I dint find out how to resolve. I had to manually link each front end application to the back end. On the biggining was only for the use of about 10 staff was ok but one year after the staff were about 40 people. Could you please send me the link of your post about auto update enabling utility?

Thansk again

http://www.access-programmers.co.uk/forums/showthread.php?t=111132