By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,493 Members | 3,090 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,493 IT Pros & Developers. It's quick & easy.

'you do not have exclusive access to the database...'

P: n/a
I recently updated one of my clients from Access 97 front-end to Access
2003. (Database still in 97 format).

They have about 5 networked PCs. On one of these PCs only, the user
gets a warning message when logging in: 'you do not have exclusive
access to the database at this time ... may not be able to save
changes'. The message keeps on reappearing. If he hits ok about 30
times, it eventually goes away.

Can someone help?
Thanks.
--
Zippy S
Oct 22 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
On Oct 22, 12:53 pm, Zippy <Zipp...@thedessers.comwrote:
I recently updated one of my clients from Access 97 front-end to Access
2003. (Database still in 97 format).

They have about 5 networked PCs. On one of these PCs only, the user
gets a warning message when logging in: 'you do not have exclusive
access to the database at this time ... may not be able to save
changes'. The message keeps on reappearing. If he hits ok about 30
times, it eventually goes away.

Can someone help?
Thanks.
--
Zippy S
1) It could be the way the data is being handled. With multi-user
systems, it makes more sense to use dbOpenTable or dbOpenDynaset
recordset types only to save a record, and dbOpenSnapshot for
everything else. This is quite different from the historic method of
opening all tables for read/write when the program is opened and then
closing them when the program exits.
2) It could also be a known bug of the .ldb file in Access 2000/2003.
If I recall correctly, the fix was to keep one table open all the
time, perferably an empty table, so it would not conflict with the
rule stated above.
3) It could be a difference in references between the computers too.
Open a form in design mode, and view the code page. From there you
can select References from the Tool menu. Make sure the same items
are selected on all computers. You may need DAO 3.51 instead of 3.6
to get this to work... I'm not sure whether DAO 3.51 works with Access
2000/2003, but Access 97 databases work well with it.

Oct 22 '07 #2

P: n/a
In message <11**********************@q3g2000prf.googlegroups. com>,
OldPro <rr*******@sbcglobal.netwrites
>
1) It could be the way the data is being handled. With multi-user
systems, it makes more sense to use dbOpenTable or dbOpenDynaset
recordset types only to save a record, and dbOpenSnapshot for
everything else. This is quite different from the historic method of
opening all tables for read/write when the program is opened and then
closing them when the program exits.
2) It could also be a known bug of the .ldb file in Access 2000/2003.
If I recall correctly, the fix was to keep one table open all the
time, perferably an empty table, so it would not conflict with the
rule stated above.
3) It could be a difference in references between the computers too.
Open a form in design mode, and view the code page. From there you
can select References from the Tool menu. Make sure the same items
are selected on all computers. You may need DAO 3.51 instead of 3.6
to get this to work... I'm not sure whether DAO 3.51 works with Access
2000/2003, but Access 97 databases work well with it.
Thanks for your suggestions. I'm working through them.
--
Zippy S
Oct 24 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.