Version 2.0 database - linking.

[Lee]

Hi,

I have a problem with an access 2.0 database. Basically our company
has an ancient tool which has a VB front end linked to an access 2.0
database.

I've been asked to create a second tool which is a c# applcation with
a SQL database. This new tool needs data from the access 2.0
database. To achieve this I set up a linked server - all seemed to
be working fine.. The problem I have is that I cannot make any
queries via the linked server to the access database when somebody is
using the ancient tool. Any query errors out along with preventing all
subsequent users from accessing the ancient tool. The recovery from
this situation is for everybody to exit and then delete the apparently
corrupted ldb file.

I've tried converting the access 2.0 database to a later version but
the VB front end, which I cannot update or get to the source code
for, then does not work....

I've tried to move the data from the access database into the new SQL
database and have linked tables within the access database but I dont
have access 2.0 and any later version of access requires the database
be converted to a later version before allowing.

I'm looking at the possibility of creating a second access database
with linked tables to the original one and then have the linked server
go to the second database. I assume though that the same locking
problem will occur unless I can bypass the ldb/locking i.e as
readonly.

I hope somebody has followed this and any suggestions, other than the
bin, would be appreciated..

Lee

 

[Guest]

Make sure that the linked server uses Jet 3.5.
Jet 4.0 is not compatible with Jet 2.5, and causes
the problems you see.

This is not a documented bug, so don't bother
trying to find a KB article about it.

(david)