Currupt DB Unrecognized database format (Error 3343)

[RachelK]

Hi,

I was working on a database verything was completely fine closed the database did not notice anything stange I was the only person working on my db on my hard tried to oepn it and I just get this error:-
unrecognized database format (Error 3343) Access can't open database.

This has happend to me before on another database which is quite worrying. I have read up on the web and it just tells me to compact and repair but when I open access with out the file and try to click on compact and repair it comes up with the same error message. I was wondering if there is a sperate compact and repair application or is there any thing I can do to salvage this database.

 

[tman72]

Before you start doing anything, backup the database you do have even though it doesn't work. From a command prompt try typing in the folloing: msaccess /decompile c:\path to your database\your database name.mdb. From there try getting into it and try compiling. Another option would be to import all your tables, forms, queries into a new database.

Todd

P.S. Do you have the latest service packs installed?

 

[RachelK]

Tman72,

Thanks for you help I have tried importing it into a new access database and I am still getting the same error message. I have tried doing what you said in dos and I am getting :-

'msaccess' is not recognized as a
operable program or batch file.

Any other idea's thanks for you help.

Cheers, Rachel.

 

[tman72]

What version of access are you running?

 

[RachelK]

I am run 2003 but the file format is set to default to 2000

 

[tman72]

Rachel,

Try running the decompile from the run box in the start menu: msaccess /decompile "c:\yourfoldername\yourdatabase.mdb"

Be sure and make a backup copy before you try this method.

I guess one thing I would try if that fails is to import your tables into a new database and test that out, and then continue on with some of your forms. Just import a few things at a time and test before importing more. One of your forms, reports or queries may be corrupt and could be causing your problem. Not sure if any of this will work, but worth trying if you can save some of your data and work you've put into your app already.

Hope it works out for you.

Todd

 

[RachelK]

No still getting the same error message.

 

[tman72]

Can you locate your ODBC data source administrator? If so, under the User DSN tab, add a new source using the microsoft access driver (*.mdb). When prompted for data source name, choose select and point to your database. You should notice the option to repair or compact the database on the form. Try repairing or compacting from there and see if that works.

 

[RachelK]

Your right I can see the option to repair there but when I click on the select button to select the mdb file they are not showing in the list as it is an un recognizable format.

 

[tman72]

I'm stumped. Did you browse to the folder where your database is and nothing was there? Or did you try and repair it and got an error that the file was unrecognizeable?

 

[RachelK]

I browsed to the file using the select button on ODBC. I worked on the database yesterday tested everything was working fine and booked the file into source safe sent it off to the customer the customer could not open hers. I could not open mine and the one on the network could not open. This has happend to me twice this month. I had to re do all the work and I was just wondering how this could be avoided for future. I have investigated on the web I was advised to update my service pack still no joy. Don't worry I just hope it does not keep happening. Microsoft said this error happends on close when a database does not close properly. I definately did a compact and repair before close as this is the standard procedure. Never mind it just one of those things. Thanks for your time and help much Appreciated. Cheers Rachel.

 

[LampknLn45]

I've had similar problems. Try to create a System DSN for the DB (start|settings|control panel|administrative tools|data sources (ODBC)) and in the same section where you select the Access DB for the DSN to point to, click the Repair button. I've had this repair my DB to the point that I could at least open it. However, this process doesn't always restore my relationships properly. I've also noticed this creates some weird records in one of my tables. In these records all fields are # sign values. One time I had 5 such records, another time I had 8. Go figure. I'm not sure what causes this and it may not happen with your DB. Be sure to check it out. I also am not sure if the # signs have replaced previously good values or if they were simply inserted. Whatever the cause, it is very annoying. I didn't write this database, but unfortunately I have to support it. Hope this is of some help.

LampknLn45

 

[RachelK]

No sorry it was my fault I was looking in the wrong folder working on to many db's but I still cannot repair the file from the ODBC. Oh well it seems access has it own personality. Rachel

 

[LampknLn45]

Sorry about my previous post. I should've have read ALL the replys before replying myself.

LampknLn45

 

[tman72]

I've experienced other corruption issues myself. Various different things cause them and I'm not sure what you can really do to keep some of them from happening other than staying up to date on servie packs. I've had pesky users that just shutdown their computer and go home for the day, but forgot to close out of the database, which leaves me with a corruption problem to try and fix. Other users were not on the correct service pack which created other headaches. Mostly trial and error is what seems to have worked for me in the past when it comes to fixing corruption. Also make sure you make a good working copy before you do any development or enhancements. Sometimes a simple change will create big problems and having a good copy to revert back to will save lots of time. I wish you well in finding a good fix to keep this from happening in the future. Access does seem to have a mind of it's own at times.

 

[RoyVidar]

I've no experience with this particular error/corruption, but here is a general link on Corrupt Microsoft Access MDBs FAQ. Click the link on symptoms and search for "Unrecognized" or 3343 for some info on it. There are also links there, amongst other to Microsoft (for some explanation and download of the JetComp utility that perhaps might work (haven't tried it)) there are also links to commercial "rescue" companies.

During the last years, I've resolved all my corruption issues using the /decompile option, which is alredy described in the thread, here's a link on "the complete process" Decompile or how to reduce Microsoft Access MDB/MDE size and decrease start-up times. I've tested the decompile on a 2003 setup, it works there too. I didn't need to specify the full path of the Msaccess.exe, but try that (as in the above link).

Sometimes the "Unrecognized databaseformet" occurs because the .mdb file has been opened from another application (Excel, Word...) and saved again. Then I believe the file might be permanently damaged.

Here's also an option that might provide some means of backup outside Access Thread705-834817 - using this you could have a "text file version" of the database as additional backup...

Roy-Vidar