Question Corrupt access front end accdb after mixing office versions

Jon-G

Registered User.
Local time
Yesterday, 16:28
Joined
Sep 12, 2011
Messages
19
I have a problem with a DB I started work on a couple of years ago in Access 2010. I fired it up last week and now I'm getting an "unrecognized database format" error when I try and open the front end.

I left this project sat after the company lost interest in finishing it. Since then I worked on another project on the same dev machine which required me to install Access 2007. I had both 2010 and 2007 installed at the same time and I remember opening the now problematic db to take some snippets from some code in there for use in the other project. Im pretty sure I only opened it in 2010 at that time.

Now the company has shown interest again I need to finish the project.

Ive tried uninstalling all instances of Office and the Access Database Engine (I needed this to test the 2007 project) running a clean up and putting a fresh install of 2010 back, but Im still getting the same error. Ive tried importing the objects from the accdb file into a new db but access still throws the unrecognized database format error. The same error is given if I try to decompile as well.

Today Ive tried uninstalling office 2010 and putting a clean 2007 install to see if I can open/decompile/import from the older db under that version of access but Im faced with the same error.

The file server where I backed up to has been rebuilt since I worked on the original project and I thought that the accdb file might have been corrupted during this process as Im pulling it from the old vhd. I've also pulled backups from several locations and all the files give me the same error. Ive even tried running them on one of the clients where I know it used to work and has not been had office tampered with since I was last looking at this and still I get the same error. I know that I had compact and repair on exit set on the front end and Im wondering if I managed to inadvertently use 2007 and the last time I opened it and royally screwed it up unknowingly creating a little surprise for me here two years down the track!

I have even tried installing an "Access Recovery Toolbox" util to see what that could make of the file, and it pulls absolutely nothing back in the report.

I have a much older version of the db which works on my dev machine but Im at a massive loss if I have to start work from this version as I made some very significant changes between these versions including changes to the back end table structure.

Any light anyone can shine, even if it just means getting the VBA out into a text file would be really helpful!!

TIA
 
Opening a new database and importing everything from the corrupt database helpt me lots of times in the past.
But it seems to me you tried every conceivable method i could think of.
I don't suppose you want to upload the database to try and get your things back?

Did you try to do it by using code?
Start a new database in Access 2013. Because they are always downwards compatible.
Open a database object (of the corrupt database) and import your code locally or export it to a text file?

HTH:D
 
Hi Guus thanks for your reply. I just tried putting a clean Access 2013 on a vanilla test rig then tried to import the objects from the old accdb file, but my favourite error still comes up when I point Get External Data wizard at the accdb. I can share the file with you if you would try it your end to see if you can get in to it?

PM your email address please!
 
Does anyone else want to chime in see if they can help me on this? I'm at my wits end!!
 
I was able to open the DB in Office 2010 after I downloaded it (of course it cannot find the linked tables). I did have to open it exclusive to able to do anything with it.
 
That's great news!! I've no idea why it doesn't work on any of the machines I've tried it on! Is there any chance you could run a compact and repair on it and uploaded it again somewhere for me to try again this end?
 
I just use a full version of DataNumen Access Repair to repair your database, and it is recoverable. But the fixed file is only about 152KB so I am not sure if this is valuable to you. I have attached the fixed database.

Below is the repair log:

Analyzing the source file...
--------------------------------------------------------
Create table 'f_D84DF6F9936F4D97BDFE52C7BD040E81_Data'.
Add 2 records.
--------------------------------------------------------
Create table 'lookupEstadoPropiedad'.
Add 5 records.
--------------------------------------------------------
Create table 'Nums'.
Add 10 records.
--------------------------------------------------------


If you have more database files, you may also send them to me so that I can use the tool to repair them. Or you can just download the software from DataNumen and repair by yourself.
 

Attachments

Hi,
Thanks for the support guys.

@copper: Ive had a look at the file you send and it appears that DataNumen has just pulled what it could from the tables. There is none of the code from any of the forms in there :(

@Kevlray: I think you might have the key! Please could you run a compact and repair on the file for your machine and send it back to me? Hopefully Ill be able to start again from there!!
 
Isolate the front end in a place where it can't reach the back end (e.g. your laptop) and the front end whilst holding down Shift. Hold Shift before double clicking the file to open it.
 
No luck. You can try opening it in Access 2013 or reach out to data recovery companies.
 

Users who are viewing this thread

Back
Top Bottom