Multiple Users Cannot Open Database even when no one is in design mode 2

[AccessUser22]

Okay I have a small problem. It seems that whenever someone has the Access database open, other users on Windows XP are not able to get into the application. It happens even when no one is in design mode of anything. A user can have just the database open with the database window and others on XP cannot get in. I've noticed this only with users who are on Windows XP machines although one user on XP has never had the problem. The users who are on Windows 2000 have no problem opening the database while anyone else is in it.

I checked the Tools/Options/Advanced and the database is set to shared, no locks so what is going on here. I really don't want to have to split this database and I shouldn't have to to get multiple users into it. I'm going to have the network admin check the Windows XP machines that are having the problem vs the one that is not to see if there has been any recent Microsoft updates that may have a bug in them. Anyone else have any idea? Thanks in advance.

 

[psemianonymous]

Check with the network admin to be sure everyone has full rights on that folder. Sometimes they don't have the permissions to create/delete files in the folder, which is something you need to enable the multiuser part.

This is just one possibility among many, so if this isn't it...there's still options.

 

[TheTomCat]

If your database is NOT split in to Front End / Back End, try this.

Go to Tools\Options\Advanced Tab and select Exclusive and All Locks.

Do this on EACH user.

May not make much sense but it will work.



Thomas Bailey
a/k/a TomCat

http://www.reportcop.com

 

[AccessUser22]

But when you set this in the options, aren't you setting it for the database itself and not the users machine? Why would I need to go around to everyone's machine and set the database up this way? If I change it on one person's machine shouldn't it be changed automatically when the next one opens it?

I decided to try this out anyway and my suspicions were correct. It did not fix the problem. Thanks though.

 

[AccessUser22]

Just to add, we have discovered that the users that are having problems opening the database from explorer, can open the database with no problems if they open up an empty copy of Access and then go to File - Open and select the database. We are still testing to see if we can come to some sort of conclusion as to why it just doesn't let them open it from explorer. Any more thoughts or ideas are welcomed.

 

[TheTomCat]

Ideally you should split the database into front end / back end. If you do that, then the settings would be Shared and No Locks.

Without spliiting it up, the ONLY way I have ever gotten it to work is Exclusive and ALL Locks. It needs and every machine including the server.

I don't know why your's doesn't work that way. Other than that, I have no idea to fix your problem without Splitting it up.

P.S. I have Never had a problem with multiple users accessing data at the same time using Exclusive and All Locks.

Good Luck. Just trying to help.

Thomas Bailey
a/k/a TomCat

http://www.reportcop.com

 

[AccessUser22]

I appreciate your input but it didn't work when I tried it out on our end. I've never had a problem with multiple users being able to open a database that was not split. The only time I've noticed it is if someone is in design view of something. With our current situation, no one is in design view. So it's just weird. Glad it works for you.

Thanks for you help.

 

[psemianonymous]

File->Open has an option for opening in exclusive mode, which I believe is unchecked by default, whereas if they double-click, it checks to see if that profile is set to "open exclusive by default", then opens in exclusive mode.

What I'm telling you is to do what Thomas mentioned above--go to each computer and make the settings change. If you're lazy ("selectively industrious") you can figure out how to make a registry script that does this for you.


Have a nice day. --Peter

 

[AccessUser22]

If you open it exclusively, isn't there not supposed to be a locked file created? We are still getting the lock file when we are experiencing the problem. I checked the machines and no one is set to open exclusively. When we have the problem, the Windows 2000 machines can access the database. The only difference is with the Windows XP machines. They can not click on the file directly from Windows Explorer. They have to go through Micosoft Access, file open to get it to open up. If no one is in the database, the people on XP can just double click from Windows Explorer and the database opens. So it's not solely an opening issue anymore. It's more of a function of how they attempt to open the database.

 

[psemianonymous]

Have you actually looked at Thomas' first suggestion? You still haven't acknowledged doing so. I'm still convinced that's the problem/fix. --Peter

 

[TheTomCat]

Another thought!!!!

Are ANY of your users using Access Runtime?

If so, upgrade to FULL Access and go back to my First suggestion.



Thomas Bailey
a/k/a TomCat

http://www.reportcop.com

 

[AccessUser22]

I did acknowledge that I tried it the other day. It didn't work when I tried it, but when I tried it on two different machines today, I was successful. So I will give this another shot on Monday and Tuesday of next week when the full staff is in.

No one is running access runtime so that's not an issue.