Access 2003 causing problems with Access 2000 file

[BlakeK]

We have an Access MDB that was created in Access 2000 and has been running for 2 years without problems, and our entire user base was running Access 2000.
Recently, some of the users got upgraded to Office 2003.
For awhile, everything will rok fine.
Then, people will start to get errors like, "The file is not an Access database, or needs to be repaired", or they will just have a General Protection error where Access will crash and they get that "Send a Report to Microsoft" type message.
I can Repair and Compact the database (in Access 2003) and it will be OK for awhile, but then someone will get the error, and I will have to Repair and Compact it again.
It was happening once or twice a week. It has now happened 3 times today.
Any ideas WTF is going on?
I can't convert it to Access 2003 file format, because we still have users on Office 2000.
I have also done the "Decompile" routine, and then done a repair and compact, and it still worked for awhile, but eventually the errors started again.

 

[MD5150]

Access 2003 *should* run Access 2000 no problem since 2003 uses a default file format of 2000. But I also found that something is not right. What it is? I don't know.

One of my customers was having the same problem you are having, even after installing all of the recent service releases. I didn't have much time to troubleshoot the problem, so I just forced everyone to use Access 2000 and the problem never happend again.

I wanted to try creating a new database file using 2003, which would create a 2000 database, unless your options are set to 2003. Then import all of your objects into the new file, thinking that maybe the fact that 2003 created the 2000 file might run better. Give it a shot. Otherwise, search the web and MS for a known bug.

This behavior is not always the case. I have another customer who runs one of my 2000 multi-user databases using Access 2003 without any problems at all.

If you don't find a documented bug, then look into all the possible causes; out-of-date service releases, jet update, wireless connections, network issues, multi-user issues.

Mike Dorthick