Access Runtime Unrecognized Database Format

Question

Hello. I developed an app in Access 2010 (ver 14.0.6112.5000 32bit) and packaged it as a runtime with the Package Solution Wizard. I executed the setup on my machine where it installed successfully and the app opened up and works fine. However, when I deployed it to a couple other machines in my office (same version) the installation succeeded but when I tried launching the accdr it threw an Unrecognized Database Format error.

---

Darrell H Burns

Answer 1

I don't know the exact nature of the problem, so let go over the basics and try and figure out what is going on.

• Now you are certain all the computers are running Access 2010?
• Are they all running SP1?
• Are their respective OSs up-to-date?
• They are all 32 bit version of MS Office?
• Your database compiles properly?  Without any errors?
• You've preformed a compact and repair?
• Have you tried using the accdb or accde just to see what would happen?
• Did you define a trusted location for the database file?

I know you see this error a lot when you develop a database in 2010 and then try and run it in 2007.  This isn't the case here is it?

---

Daniel Pineault, 2010 Microsoft MVP
http://www.cardaconsultants.com
MS Access Tips and Code Samples: http://www.devhut.net

Answer 2

Doh! I goofed. I was packaging an older version (12 instead of 14) of AccessRuntime.exe that I still had from A2007. Once I packaged the A2010 version all went well...except for the trusted location nagbox, which I was able to overcome in my AutoExec.

That's a good checklist anyway, Dan. Thanx for your time.

Darrell

---

Darrell H Burns

Answer 3

Excuse me. I have a similar problem.

But it only happens on a customer machine where Office 2007 is installed.

I'm using an accdr(compiled before) and that's the file that fails, doesn't even open. Message is 'unrecognized database format'.

I'm shipping accessruntime 2010 32 bits (correspondent to my office vs), apparently it fails, but that must have worked at least once(the guy can't remember what happened the 1st time), since if it's not installed, it installs, and if you try to install it again, it just fails.

It pretty much seems related to Office 2007 being installed, but shouldn't it open despite of it, because of access runtime?

That's it, Daniel.

I hope You can give me a piece of advice on the matter of this subject.

Thank You.

Answer 4

The Access 2010 runtime does not include SP2. And more noteworthy is the windows update and even issuing the SP2 update to office will NOT update Access runtime.

You thus want to install the SP2 (or 3?? Now) update to the Access runtime. This is a separate download and install.

Normally Access will work/run without the SP updates, but the SP2 2010 update was “challenging” since if you compiled and developed your application using full office SP2 (which is likely), then compiled accDE applications would not work with 2010 runtime which is without the SP updates.

Interesting, is an accDB (non compiled) WILL run since it includes source code, and the VBA can re-compile on the fly (and this automatic re-compile even occurs with a runtime only install).

So I would install the Access 2010 SP2 update on those machines.

Regards,
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada

Answer 5

Thanks, as usually, Albert!

So, You think that should be enough? Because I got this one guy, he bought an app, and He's got like 1M machines, each one with specific settings, and one never knows what's the next chalenge. If it's running office x86/x64, if it's running older vs like 2007, I see myself in a real tricky situation. I'm almost giving up access and rewritting it in .NET.

Anyway... I see that installing Access 2010 where Office 2007 seems hard time!