Error Accessing MSAccess database on network drive

Hi,<br><br>On a network drive accessed by all users,I have created a directory with all security permissions to everyone. Copied the MSAccess database to this directory and granted full control to Everyone.<br><br><br>From a personal web server on my machine , I am trying to access a MSAccess database on a network drive and get the following error.<br><br>I also created a folder on my C: drive.<br>When I change the database path/namt to clannedactivitypact.mdb everything works fine.<br>But when I try to access the database on the network drive, I get the following error<br><br>Error Type:<br>Microsoft JET Database Engine (0x80004005)<br>The Microsoft Jet database engine cannot open the file 'gperationssupportplannedactivitypact.mdb'. It is already opened exclusively by another user, or you need permission to view its data.<br>/html/html/Jon/jon_entry.asp, line 79<br><br><br>Browser Type:<br>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) <br><br>Page:<br>GET /html/html/Jon/jon_entry.asp <br><br><br><br>Would appreciate some help with this<br><br>Thanks<br><br>Craig

This is the actual error message<br><br>Glannedactivitypact.mdb<br>--Provider=Microsoft.Jet.OLEDB.4.0;Data Source=Glannedactivitypact.mdb;Persist Security Info=False;-- <br>Microsoft JET Database Engine error '80004005' <br><br>The Microsoft Jet database engine cannot open the file 'Glannedactivitypact.mdb'. It is already opened exclusively by another user, or you need permission to view its data. <br><br>/jon_te_start.asp, line 32

Try using the UNC path rather than a mapped drive. This is because the user context under which the database is being opened may not have a G: drive mapped.<br><br>(Should always use UNC paths).<br><br>Eg: \server1sharedirectorydatabase.mdb<br><br>http://www.able-consulting.com/MDAC/ADO/Connection/OLEDB_Providers.htm#OLEDBProviderForMicrosoftJet<br><br>Cheers,<br>Andrew

Hi Andrew,<br><br>I copied the database to a new one and tried accessing it to make sure nobody is using it. I can open the database using MSAccess. I still get this error<br>\englgnt003GroupOperationsSupportplannedactivitypa ct.mdb <br>Microsoft JET Database Engine error '80004005' <br><br>The Microsoft Jet database engine cannot open the file '\englgnt003GroupOperationsSupportplannedactivityp act.mdb'. It is already opened exclusively by another user, or you need permission to view its data. <br><br>/html/html/Jon/jon_te_start.asp, line 38 <br><br>Thanks<br>Craig

Do that user you have write permissions in the directory where the database is located?

I have the same exact problem on any machine on my network that isn't mine (the one I created the mdb and the vb application from). Haven't yet resolved it either. I did find one interesting thing. One user's machine (Windows 2000 pro) would give the same error. However, I created a shortcut to the vb executable (front end) and specified to run as another user. When I run it as my username, password and domain, it runs JUST FINE. If I do anything else, it does not work unless it is from my machine. You would think this is simply a permissions problem with the database, database file, or the network folder, but the network folder and database file both have full permissions for eveyone. I even tried giving full permissions to the individual users but the same thing happens. When I open the access db itself, I check Tools>options>advanced to make sure it is opened shared and not exclusive. It shows shared. However, If I try to modify any security settings, I get a message that says the database is opened esclusive and asks me if I would like to switch to shared. What? I'm sure MS would say its a feature, not a bugg. I never had this problem until I started using access 2003. Previosly, I used access 2000 instead and never ran across this problem. Apparently, it is a fundamental problem with Access. Apparently MS isn't fully utilizing their R&D team for vb and access.

For goodness sake! This is what most people use vb and access for, but nobody seems to have an answer that helps. Hopefuly someone smarter than me can take this information and make sense out of it.

Gee, do you think anyone from this thread is still reading 18 months later.

Don't bring old dead threads back to life.

If you want to share an MS Access database with multiple users and avoid the file sharing, locking that MS Access does in the .ldb file or the file locking that your lovley network often screws up then SPLIT YOUR DATABASES. Tables in one single repository database called (database)_be.mdb (stands for "back end") which lives on ther server, and the front end file (database).mdb with the forms which lives on the client machines. The only issue is keeping everyone current when you make changes to the forms, but just keep the published version of the front end in the same network path as the file you are currently haveing trouble with and instead of users opeining it they simply need to copy it to their desktop whenver you tell them to get an update. Do this and you should never again get the "opened exclusively by another user" error. Access is not very good at sharing an un split database.

You can split your databse by using the wizard in Tools, Database Utilities, Database Splitter.