I have been working on this DB for past several years. Sometimes while working from home, I e-mailed the updated version to and from work. How To Program 2010 Nissan Intelligent Key. Since last week, something went wrong. I couldn't open the DB at work, although it works fine on my laptop. I keep getting this error message: 'Unrecognized database format: 'U: pathname filename.accdb' So I made a copy of the file on a flash drive from my laptop and tried to open it using my desktop. Still getting the same error message.

What is wrong? I spent more than 6 hours worth of works on it past weekend.

Access Database Problem: 'unrecognized database format'. Microsoft Access / VBA Forums on Bytes. May 20, 2013 When I execute the following code I receive the Error 3343: Unrecognized database format. Microsoft Office 12.0 Access database. Error, but it seems the message.

Need to open the file and get going. Can someone please give me some direciton? Frequent backups are an absolute requirement when working with MS Access. I have learned that the hard way. That being said, you're in the soup now so we should try to pull you out. You might be able to extract all the goodies out of it by creating a new database and importing the tables, forms etc.

There are also recovery programs available from a variety source. I believe when I last solved this problem I got by with a trial version of one of those tools, but I can't come up with the name now. I'm sure some other experts will have additional guidance. I cannot even open the DB.

Therefore, importing any forms or queries not possible. Yes, I have a back up copy (my DB is backed up every day at the end of each day). I just don't feel like recreating 6 hours of work. Yes, a form is executed on startup.

What is puzzling is that when I worked on it at home, it worked just fine on my laptop. Eventhough the original was an e-mailed version (from work to myself).

I just can't get the DB to open at work using the work desktop. Thanks for taking the time to help me. MNNovice, My initial thought is that it sounds like your work DB might be in MS Access 2007 and your home in 2010? Although MS 'told' us that these two versions are 'compatible', they are definitely not--especially as it concerns the Tables themselves. Jim, that is a smart workaround, and just might save the OP's work. Additionally, I echo his advice for frequent (or should I say, 'constant') backups of your work. You can always get a bigger (or another) hard drive, but you can't get back lost work.

Twinnyfo & jimatqsi: Thanks for your tips. Yes, I have Access 2007 at work and 2010 at home. But this didn't cause any problem until a week ago. Yes, I compress and repair each time I close out the DB no matter where I am. But this didn't resolved the matter. Yes, I save a back up copy of the DB at the end of each day before heading home. When I am at work and email a copy from work to my personal e-mail - I have no problem opening it.

But when I e-mail the same copy from home I cannot open it at work the next day. I tried making a second copy on a flash drive, that didn't help either. I also don't have problem opening the DB from home that is mailed from work. This is driving me crazy. I wish I knew more.

Thanks to both of you for your time. If you want to continue working from home then you could try adopting the following approach: • Work on DB at work. • Transfer latest version to home at end of day. • Work on various objects in the DB at home. • Make a note of each object changed during your home session. • Transfer updated version to work when done. • Starting with the latest version you have saved at work (IE.

The one you sent home the previous time) import from the new one transferred from home all of the objects changed in your home session. If any fail to import or crash afterwards upon use then revert back to the original copy of the object.

This isn't foolproof, but it should leave you with problems only very rarely, and those will be limited only to individual objects rather than your whole database. Needless to say, always keep your backups just in case.