Strange Access error/behavior

[BrianWen]

I maintain a large Access database that contains a lot of scripts, hundreds of elements like forms, queries, tables, reports and such.
The user base is between 50 and 100 people. The users get the database in ACCDE format, while I keep the ACCDB for further development. This has worked so far. They have a current ACCDE running and a works just fine. Now, I took the ACCDB, made a few very small changes, created a new ACCDE, which works just fine for me. But the users cannot execute the new version.

They get this error:
"Class does not support Automation or does not support expected interface".

I've Googled the error, but most sites discuss the error in VB6 or .Net.

The code changes I made had nothing to with advanced connectivity or the likes. I think I've had my computer reinstalled since my last publish of a version. And in this reinstall, I've gone from Windows XP to Windows 7 64-bit. Same version of Office, though (Office 2007 SP2).

It's something when I compile the ACCDE from the ACCDB, because they can run the ACCDB just fine.

Has anyone got any good ideas?

 

[Andrzejek]

I've gone from Windows XP to Windows 7 64-bit.

My guess would be the change in OS on your machine is the problem cousing part. And I would guess your users have XP as OS, which is 32-bit. Most of old 32-bit pieces on Windows 7 are places in WOW (Windows On Windows) parts on your machine which emulate Windows 32-bit on Windows 64-bit.

Try to go back to Windows XP

Have fun.

---- Andy

 

[BrianWen]

Exactly...Thank you!

I made a Virtual PC with Windows XP and compile the database from there...