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

Could not use ABC.mdb; file already in use.

P: n/a
I'm getting this message when starting application A (Access 2003),
while Application B (Access 2.0) is running.

ABC.mdb is a back-end Access database (2.0) that has shared tables
with links in both applications A and B.

This problem does not exist when application A (2003) is started first
(before application B (2.0)! It seems that A2003 cannot read .ldb file
created by A2.0, however A2.0 can read .ldb file created by A2003!

For now, I'm getting around this by opening all back-end databases by
some A2003 front-end, keep it open all time. But I'm looking for a
more robust solution.

Please note: upgrading applicationB (2.0) to Access 2003 is NOT an
option!

Thanks for reading

Mourad

Oct 9 '08 #1
Share this Question
Share on Google+
2 Replies


P: n/a
ARC
The only thing I can think of is checking to see if the "Open exclusive" box
is not checked when starting App B. I don't think that checkbox should
affect the back-end db, but worth a look.
"Mourad" <mo************@gmail.comwrote in message
news:b1**********************************@z6g2000p re.googlegroups.com...
I'm getting this message when starting application A (Access 2003),
while Application B (Access 2.0) is running.

ABC.mdb is a back-end Access database (2.0) that has shared tables
with links in both applications A and B.

This problem does not exist when application A (2003) is started first
(before application B (2.0)! It seems that A2003 cannot read .ldb file
created by A2.0, however A2.0 can read .ldb file created by A2003!

For now, I'm getting around this by opening all back-end databases by
some A2003 front-end, keep it open all time. But I'm looking for a
more robust solution.

Please note: upgrading applicationB (2.0) to Access 2003 is NOT an
option!

Thanks for reading

Mourad
Oct 13 '08 #2

P: n/a
Thanks for your input,

Both front-ends are opened in shared mode (exclusive is unchecked),
otherwise the behaviours would be the same when I start 2003 first!
It is that 2.0 layout the header page of the back-end mdb in a way
that is interpreted by 2003 as the database is being locked/in use.
Oct 13 '08 #3

This discussion thread is closed

Replies have been disabled for this discussion.