Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Access multiusers

Status
Not open for further replies.

NWTrust

Technical User
Apr 2, 2002
68
0
0
GB
With Access 97 on a network server several users could access a database at the same time. Now, with Access 2010, this facility is no longer present. Is there any way of restoring it, please?
 
This shouldn't be an issue with any version of Access. Is anyone opening the file exclusively? Is a locking file created on the server?

BTW: the recommended method for deploying any Access application is to split it into a back-end file of just tables and a front-end of the forms, reports, query, code, etc. Every user should have their own copy of the front-end file.

Duane
Hook'D on Access
MS Access MVP
 
dhookom is exactly right.

Access has long been unreliable when multiple users access the same front-end file at the same time. The front-end/back-end setup is the only way you should have a multi-user Access environment.
 
Thank you both! Look's like splitting the d/b is the answer.
NWTRUST
 
The reason is that after Access 97 object edits (sorting, applying a filter or any other minor changes you may make and maybe never even save) began taking an exclusive lock to the file. Splitting gives you performance gains anyways.
 
With four or five databases and half a dozen users, some of whom request changes and additions to the databases, splitting is a last ditch solution. Fortunately I have discovered a simpler answer. The databases were all created in Access 97 and latger moved to Accesss 2010, retaining the .mdb extension. I have now renamed them to .accdb and with no other changes they are now accessible by multi users.


 
Just because it is simple does not make it a good solution. This is a bad design. Inefficient, difficult to maintain, and prone to corruption. Split the db and learn how to effectively deploy the front end. No one here will recommend this as a good idea.
 
In addition to echoing MajP's comment that you should definitely split...


Did you convert your database to Access 2010 or simply rename the file? Renaming would not change the database internals. I've never tried it and have no idea if it would open... Excel on the otherhand, doesn't much care what the extension is, it will detect and read many compatible files with the wrong extension.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top