In our office we have several Access databases operating which are stored on our server so that others can use them. They are all 2007 files. Only two -three users have access to these files. Now, I have brought this up before and you are probably cringing about not having split these files (front end, back end) but this has not been necessary due their infrequent use. The other users are opening all of these files (with the exception of the problem file, OfficeDat) with their 2010 versions of Microsoft Office Access and have no issues. The file in question (OfficeDat) however can only be opened on my computer (I do not have Access 2010 but only 2007). If opened on other computers, it is corrupted. The only difference between this file and the others is that it has a password to access it (i.e. encrypted). Recently, we have tried several things to solve this problem: I have split this file, I have removed the password, I have recreated a new file with no password by transferring tables, forms etc. to a new file, we have replaced two of the users computers and purchased new Microsoft Offcie Professional software. Despite these efforts, the OfficeDat file still is corrupted by other computers. Obviously, I would like it to be used by others but also I am worried will accidently be corrupted (I do back up regurlarly). I have included the messages that occur when an attempt to open the file by the other computer (other than mine): 1.'An error occured while loading 'Report_STAFF5'. Do you want to continue loading the project? Yes or No', click yes then.. 2. This message appears 'The database cannot be opened because the VBA project contained in it cannot be read. The database can be opened only if the VBA project is first deleted. Deleting the VBA project removes all code from modules, forms and reports. You should back up...."

What ever I try the file is permanently corrupted. Can someone help me with this?

Hi Mowat,

Not exactly sure what you mean by the file/database is getting "corrupted." Is the data still okay after the file gets corrupted? Are the other users on 2010 machines making any changes to the database design? Or, are they just trying to use it to get to the data.

I believe "splitting" the database would protect your data better because the only thing that could get corrupted would be the front end. Not sure how complicated your database is but if you split the db, can you try creating a brand new front end from the 2010 machines to see if they can safely work with the data?

Just my 2 cents...

I'll backup DBGuys suggestion on splitting your db.
You can try Stellar Phoenix Access Recovery (A2010 supported).

Hi DBGuy,

Thanks for answering. What I meant by corrupting is that the front end file no longer has a Switch board once someone else has tried to open it. The 'back end' file is OK.No one(other than me) touches the database design.