M
Mourad
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
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