hvserv
asked on
Trouble opening Access database
We have an Access database on a file server which occasionally (from one workstation) refuses to open from Explorer. It will open from Access. A copy of the file will open from Explorer. File will open from Explorer on other stations and the server. This problem seems to reoccur every few months, the usual fix is to create a new copy and tell everyone to use the new copy. Would like to find the real solution to this.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Always put a copy of the database front end (application) on the users PC! DO NOT share the application with multiple users on the File Server!
You can however link the front end (on users PCs) to the data (back-end) on the file server, this is actually the preferred method of sharing an Access database application across multiple simultaneous users.
You can however link the front end (on users PCs) to the data (back-end) on the file server, this is actually the preferred method of sharing an Access database application across multiple simultaneous users.
ASKER
Thank you to all who commented. Had assigned points to first expert prior to receiving subsequent answers. This problem is an inherited problem for me, and I have minimal experience with databases. Examination of our configuration indicates an overhaul is needed.
hvserv,
Regarding my comment about putting the front-end application on the users PC. There are a number of ways to do this. One is with a simple batch file on the desktop, which has commands to:
1. delete the current version of the application from the users machine
2. copy the version that is on the server to the users machine
3. Start Access and open that new database.
This addresses boag2000's comment as well, and ensures that if you need to make changes to the application, all you have to do is copy the updated version to the file server. The next time the user clicks on the batch file shortcut, it will copy that file to their computer and use it.
Regarding my comment about putting the front-end application on the users PC. There are a number of ways to do this. One is with a simple batch file on the desktop, which has commands to:
1. delete the current version of the application from the users machine
2. copy the version that is on the server to the users machine
3. Start Access and open that new database.
This addresses boag2000's comment as well, and ensures that if you need to make changes to the application, all you have to do is copy the updated version to the file server. The next time the user clicks on the batch file shortcut, it will copy that file to their computer and use it.
(Also, if you use a shortcut you can supply various start up options for the database)
(Why force users to navigate explorer anyway...?)
;-)