You do not have exlusive access to the database at this time. Erro

[Alex B.]

I have an Access application on a network share. It's been in production for
several years without being changed. Recently a couple of users began
getting the error message in the Subject line (I'm thinking as a result of
some "fix" pushed out by MS). Found an article on the Net that suggested
opening and maintaining a separate connection to prevent this. Tried
it...didn't work. I also implemented user level security and only granted
Open Exclusive on the DB to a special "admin user" account I setup...still
didn't fix the problem. This user has Modify rights on the share, just like
everyone else. Furthermore I can log into her machine and open the db just
fine and I don't get the error message!

Anyone know what the fix for this is? I'm about ready to try DYNAMITE!

 

[Pete D.]

Sounds like a rights problem if you can do it and user can't. Check user
rights for the share, directory and make sure they match yours.

 

[a a r o n . k e m p f]

wow.. this sounds to me like Jet has thrown a tissy and decided not to
work as it should be.

at this point-- this is when I start reccomending that you move to SQL
Server
User Level Securiy in Jet sucks so bad that they removed it from the
Access 2007 VERSION

 

[Pete D.]

Well you missed the point again...and for you this one is really off base!
I thought you were at least at the user basic level. Try thinking like this
a a r o n , If I can do it and he/she cannot and I'm on the same computer
then what do you think is the one common factor. Must be the user. Now
step by step, the share was mentioned...as far as I know taking it back to
the beginning screams network rights. Now there are a few and I mean a few
where it can mean workstation rights but usually it would be installing or
maybe control of a subdirectory that someone must write to or changes to the
registry. So, if you car suddenly dies on the side of the road do you check
the gas gauge or do you just pull the engine and put in a new one?
Reminder, suction, ears, pull head out!

message
wow.. this sounds to me like Jet has thrown a tissy and decided not to
work as it should be.

at this point-- this is when I start reccomending that you move to SQL
Server
User Level Securiy in Jet sucks so bad that they removed it from the
Access 2007 VERSION

 

[Pete D.]

Thank you, I had seen this error before but only if I entered and edited the
design while others were in it. I then stopped doing that but never
understood the open exclusive permission as I split it and stopped causing
the problem by fixing and replacing the frontend. Again, thanks, Pete
(Sorry about my attitude, I have have been being followed lately by
someone.) Pete

 

[Tony Toews [MVP]]

Jet 4 prevents you from making design changes when others are connected to
the db because it might corrupt the db file. Jet 3.5 didn't have that built
in safeguard and had lots more corruptions.

Also Jet 4.0 saves all the VBA code as a blob in a single record in a
system table. Whereas Jet 3.5 saved the code along with the form,
report or module. Or so my understanding goes.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[David W. Fenton]

Jet 4 prevents you from making design changes when others are
connected to the db because it might corrupt the db file. Jet 3.5
didn't have that built in safeguard and had lots more corruptions.

So Microsoft claims (in attempting to justify the monolithic save
model), but it doesn't correspond with the experience of any
experienced Access developer of whom I'm aware (certainly no this
one!).