I have a web site using an access 2000 mdb file.
I have just upgraded my development machine to xp and access 2002.

If I open the original live MDB file using Access 2002 then it appears to lock the file since the web site now cannot access the MDB until I close it in access 2000.

Does anyone know if Access 2002 opens a 2000 created MDB in some funny manner that ends up locking the db from the 2000 jet oledb?.
NB I can open the db multiple times using multiple instances of access 2002!!

If you have already convert the database.

Under tools
--> Options
--> advanced Tab

check and make sure the default open mode=shared
and also check default record locking=no locks

thsnka for the ideas.

I didnt want to convert the database as some colleagues still have 2000, plus I was worried that the jet oledb wouldnt work.
However I just tried converting it and everything still works, BUT the problem stil remains . I tried different record lock types too
I had already double checked the open type, but thats correct. now I am really stumped.

Next port of call is that the 2002 upgrade is coincidental and its a security access user id issue

You can still convert it back to OLDER version and to current version


Tools >> Database Utilities >> Convert Database >> To Current Access Database Version -- and select the older version .mdb file. This creates new file of current version.

Open the Current Version .mdb file and
Tools >> Database Utilities >> Convert Database >> To Prior Access Database Version -- and Give the New .mdb file. This creates a new .mdb of older version.

In both cases, you can't overwrite existing MDB files. Only new files can be created.

But it works fine with me if I convert it to either versions. So I work with one version of MDB and later convert to the other so as to update if any structural changes made to the MDB and keep both in sync.

I dont see any problems with JET engine. It works for both the versions.

-Vijay G

Found it!.
The problem was elswhere with my upgrade.
The folder containing the mdb file had not carried over the permissions correctly, which was confusing as all programs worked on their own, but not togther.

Its to do with the LDB file, for some reason it could be deleted and created but not updated or soemthing like that.

I found it from an implication on another board

Thanks for the support