HELP!!! Access 2003 database crashes when opened in Access 2007.

[jparker1954]

After working on an Access 2003 Database for 3 years over a server that is used in 3 states, one of my co-workers decided to open up the database in Access 2007 on his computer (I believe this is the first time it's been opened in anything but Access 2003). The following two messages appeared, and the Compact and Repair Function DOES NOT work. The only thing I've been able to do that works is to restore from a backup.



I read the issues regarding the Name AutoCorrect, and those settings are turned off (see screen). The corruption still occurs

Here's my concern. 1.) How do I find out for sure what's causing this? 2.) How do I stop it so that co-workers can access the database in both Access 2003 and Access 2007? I'm desperate for some detailed advice here, as management wants the database up and working at more locations by Monday (4 business days).

The 2003 database does use Startup and Utility Functions modules that were copied from the Northwind.mdb samples.

[June7]

Is this a split design? Are users opening the same frontend file? Users should have their own working copy of frontend on their workstation.

I don't know why this would corrupt the mdb. I open mdb files with Access 2007 and 2010 without issue.

[ItsMe]

I think I was able to get a similar result in a lab environment a while back. I was trying to break files and was successful when newer versions of Accees did, not a conversion, but some sort of manipulation to an all in one mdb. I would switch back and forth between two machines, opening the file. One machine had A2003 and the other had A2010.

The methodology I employ in production is to dedicate an FE file to the users (like June mentioned). Their file will link to the shared mdb. So, the FE can be an mdb or an accdb and THAT file connects or links the MDB. I don't allow multiple versions of Access to open a single mdb file.

[jparker1954]

No, users have 3 HarvestingLog.mdb files that are linked to the main database, they enter information in that and then it appends to the main database through a series of queries. Works great in Access 2003 and has for 3 years.

[ItsMe]

...users have 3 HarvestingLog.mdb files...

What exactly does this mean? My experience is that if a file is not opened exclusively by a single version of Access you may encounter undesirable results.

[jparker1954]

Unfortunately I don't have a choice on who can open the file (2003 or 2007) and I don't see that changing soon.

[jparker1954]

Location one has data-entry database #1 where they enter their harvest records. Location 2 has a data-entry database #2 where they enter their harvest records. Location #3 has data-entry database #3 where they enter their harvest records. Once entered, I go into the Main database and click a button and the data from those 3 databases appends to the Main database. ALL those files were created in Access 2003 and have worked fine for 3 years. The first sign of trouble was when a manager tried to open the Main Database in Access 2007.