Link to home
Start Free TrialLog in
Avatar of mbizup
mbizupFlag for Kazakhstan

asked on

Exclusive Access Problem With Upgrade to Access 2003

Hi,

Since an upgrade to Office 2003 about a month ago, a few of our network database users have reported receiving the message "You do not have exclusive access to the database at this time...." when opening databases.  After clicking ok (31 times according to two people using different databases), they are able to use the databases without any problems.  

I don't think the problem is within the databases.  Here are a few other observations:
- Nothing has changed within the databases, the only difference has been the upgrade.  
- Giving these users admin privileges resolves the problem (but is not a good long term solution).  
- If I set my privileges to match theirs, I don't experience the same problem
- Only 4 out of 220 users are reporting this, and they are having trouble with all shared databases.

Any ideas?

(I won't be able to follow up on this for a few hours)

Thanks.
Avatar of Jim Dettman (EE MVE)
Jim Dettman (EE MVE)
Flag of United States of America image

This is default behavior.  Due to changes inthe way VBA code is managed, only a single user can make changes to the database at one time.

JimD.
BTW, here's a MSKB link on that:

http://support.microsoft.com/kb/200290/

which started with A2000.  Not sure what you upgraded from.  If 2000 or later, then you were already dealing with that issue and it would be somthing else.  If that's the case, check that the workgroup file and the database have different names.  Also that you don't have a MDB and MDE with the same name in the same directory.

  When Access tries to create a lock file, it lops off the extention and tries to create a locking file with <db name>.LDB  If the workgroup file and database share the same name, they end up with the same .LDB file and locking errors result (same for a MDB and MDE in the same folder).

JimD.
Avatar of puppydogbuddy
puppydogbuddy

Miriam,
I found 4 links for your error message in the MS Knowledge Base.  If the hyperlinks don't show, all you have to do is type the reference # [e.g. 83972;Q293613, etc.] into Google:

8/15/2006 839782  You receive a "You do not have exclusive access to the database at this time. If you proceed to make changes, you may not be able to save them later." error message when you try to open database objects in Access
(839782) - Explains the exclusive lock error that occurs when you try to open a form, a report, or a module in Design view in Access 2000. To work around the problem, rename or move the database file to a different folder, or open the database exclusively.

2) 8/14/2006 Q293613  ACC2002: "You Do Not Have Exclusive Access..." Message Appears More Than Once When You Edit a Module
(293613) - When you try to edit code in a module, you may see the following message, even though you just saw the same message: You do not have exclusive access to the database at this time. If you proceed to make changes, you may not be able to save them later.

3) 8/13/2006 Q200290  ACC2000: Exclusive Lock Required for Saving Design Changes to Access Objects (Q200290)
When you try to customize toolbars or open a Microsoft Access form, report, macro, or module in Design view, you receive the following message: You do not have exclusive access to the database at this time. If you proceed to make changes, you may

4) 8/12/2006 Q283228  ACC2002: Exclusive Lock Required for Saving Design Changes to Access Objects (Q283228)
When you try to customize toolbars or open a Microsoft Access form, report, macro, or module in Design view, you receive the following message: You do not have exclusive access to the database at this time. If you proceed to make changes, you may


PDB
PDB,

  Please check first what has already been posted.  I said all that already.

JimD.
Avatar of mbizup

ASKER

Jim,

Thanks for the replies.  The upgrade was from 2000.  What is perplexing me is that none of the users are attempting to open the databases in design view.  One other test I just ran shows that these users can open databases without trouble with their own accounts on other machines running Office 2003.

The MDB's and MDW's are named differently, there are no MDE's and some of the back-ends are SQL Server.  
The upgrades were part of an automated organization-wide software push, so the options made during the installation *should* be the same across the board.  

The message does make it look like the databases are being opened in design view, or for exclusive access by just these users (on just these machines), but they are using the same locally copied shortcuts as everyone else.

Any other thoughts?
Avatar of mbizup

ASKER

PDB,  

Thanks for the reply, too.  These users are just trying to open the databases as regular end-users.  What other than the shortcut might affect the way a database gets opened?
mbizup,

  Your on the right track.

<<What other than the shortcut might affect the way a database gets opened?>>

  Check the shortcut settings (no /Exclusive switch).  Also have the users open Access and goto tools/options (they'll need to open a database or create one to do so), click the advanced tab and make sure "Default Open Mode" is shared.

JimD.
Avatar of mbizup

ASKER

Jim,

I checked this on 2 of the machines...  The shortcuts are okay and Default Open Mode is set to "Shred".
Miriam,
Just got back online.
<<<<What other than the shortcut might affect the way a database gets opened?>>>>

Answer:  Opening more than one instance of Access on the same machine.  Check and see if there is an Access icon minimized.


Jim:
Sorry...I forgot to refresh my browser before sending.
Avatar of mbizup

ASKER

PDB,

I double-checked that only one database was open...no joy.  
OK, next thing is to double check the security.  All users need full read/write/delete priv for the directory where the MDB/MDE resides and the work file.

  If they don't have that, Access will attempt to open the database exclusively.

JimD.
Avatar of mbizup

ASKER

Jim,

Their directory privileges look good.  They all have read, write and delete.
ASKER CERTIFIED SOLUTION
Avatar of puppydogbuddy
puppydogbuddy

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Miriam,

Based on the above, I guess you need to check to see if there were Access add-ins or activeX's installed locally on the problem PC's.

PDB
Avatar of mbizup

ASKER

PDB,

You may be onto something.  These users might have been in a group that received additional software along with Office 2003.  I can't think of anything else that would distinguish them from the majority of the users.  I'll look into this tomorrow morning and let you know.

Thanks
Avatar of mbizup

ASKER

This handful of users all had received Acrobat Professional 7.0  with the recent software updates.  Going through add/remove programs for Acrobat Professional 7.0:
Modify... Create Adobe PDF ... Adobe PDF Maker and removing the Access option did the trick

I can honestly say I NEVER would have guessed this to be the root of the problem.  What a great illustration of the value of thinking outside the box!

Thanks for all the help.
Glad I could help.  Thanks for the complimentary remarks, points, and grade.
Nice job PDB!

JimD
Thanks, Jim.