I'm trying to share the front-end of an A2K split mdb. I copy the front-end mdb (with linked tables) on the users' desktops and leave the back-end on the server. When some users try to open the file (not a shortcut) they get a critical stop message saying that the file or one of its required libraries cannot be found and it hangs up until I have to Ctrl-alt-del out of its not-responding self. The .ldb is on their desktop afterwards, proper permissions are assigned, and I've ruled out the difference between win95/98 as a cause. Could something be locking up the back-end? This is really frustrating.
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 bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Weird shared database problem
- Thread starter dalaska
- Start date
- Thread starter
- #3
- Thread starter
- #5
The exact error message is:
Cannot find the file "\\server\share\promotion.mdb" (or one of its components). Make sure the path and filename are correct and that all required libraries are available.
I know for sure the path and filenames are correct. Is there some sort of problem creating the .ldb when an additional user connects? From what I've been reading, implementing a multi-user db is not supposed to be this problematic!
Doug
Cannot find the file "\\server\share\promotion.mdb" (or one of its components). Make sure the path and filename are correct and that all required libraries are available.
I know for sure the path and filenames are correct. Is there some sort of problem creating the .ldb when an additional user connects? From what I've been reading, implementing a multi-user db is not supposed to be this problematic!
Doug
You need to check that all of your users have the correct permissions for the folder the back-end is in. Make sure that they have create permissions which is needed to create the .ldb file and also edit permissions which are need to change any data in the file. Also, another thing you might look at is if you are using any ADO connection objects check the mode property. If the mode is 'adModeShareExclusive' or something similar the first user in would block everyone else from using the database. If this doesn't help try using the Package and Deployment wizard that comes with Office Developer. It will create a package that includes any dll's etc. that might not be on your users machines. Use this to deploy to them rather than just copying the mdb/mde across the network. Good Luck. Durkin
- Thread starter
- #7
Solved the problem (somehow). I created a new db, imported objects from the old one, created identical table links, and disabled record-locking. Also, I changed the open mode to exclusive. I think the exclusive part is the key because with the front-end being on the client PC, there's no reason to share it. Not sure what caused the whole mess in the first place, but it's gone now. Thanks for your help, guys.
Doug
Doug
- Status
Similar threads
- Locked
- Question
- Locked
- Question
