MDE created in Win7 don't run xpwin

[FuzMic]

Hi members

I created an .mde in Win7.64bit.sp1 ultimate OS running Access.02.sp3. When this is placed on the PC running xpWin.sp3.prof with Access.02 or Access.03, it reports that it failed due to Automation issues.

This .mde has no problem running in Win7.

.mde created from the same .mdb in WinXp.sp3 running Access.02.sp3 runs fine on all OS platform with access from 02 to 2010.runtime.


Any Views please.

 

[Jeanette Cunningham]

If I create an .accde in A2007 OS Win7 where I also have Office 2010 installed and try to open the db in A2007 OS Vista - it won't run due to reference problems.
I wonder if this could be related somehow to your problem.

If you have the original .mdb file, try running that on the Win xp computer.
The advantage you have with the .mdb is that you can open it with the shift key and check out the references - something you can't do with an .mde.

It could be that you need to get the .mdb db running correctly with WinXp and use WinXp to create the .mde.

 

[DJkarl]

I think Jeanette is probably right. References are horrible to try and sort out in a multi-version environment. Fortunately you can use Late-binding to solve most of those issues, though it becomes a little more problematic recently with Access changing formats from *.md* to *.accd*. Still, if you aren't using a late binding model in your production code you should be, it saves a lot of headaches later on.

 

[John.Woody]

I think the problem is deeper than that. Look at this post
http://www.access-programmers.co.uk/forums/showthread.php?t=205800&highlight=windows+7+sp1
If you compile the db on a Windows 7 PC with sp1 it won't run on Win XP.

Sorry

And here is some more
http://social.msdn.microsoft.com/Forums/en/windowsgeneraldevelopmentissues/thread/3a4ce946-effa-4f77-98a6-34f11c6b5a13
No official fix for vba, the advice is uninstall sp1 until a fix is available.... may be...... sometime.....

 

[DJkarl]

Wow, Microsoft hosed developers on this one. So you'll either need to patch everyones PC with a hotfix, un-install SP1, or compile the MDE on a different machine.

Thank you for making our lives easier MS. :S

 

[FuzMic]

Thanks for the interest of this new phenomenon.

For sharing, i have faced another shade of this issue wherein Vista OS had problem running a .mde created with xpwin.sp3 & access03.sp3 while all other OS including win7 has no problem. To overcome this i have to create the .mde specially in Vista. Like what you all said, it has something to do with Reference, here i think it was "MS ActiveX Data Objects Recordset 6 Library."

This new phenomenon however is quite different, it is in the reverse.

More: I have also tried the .mde created in win7.64bit.sp1 & access02.sp3 on a xpwin.sp3 pc running on Access 2010.runtime and the problem manifest the same way.

Still hoping to pin point the culprit, else we just got to create all .mde in winxp. Hope Microsoft have something to say about this.

 

[Jeanette Cunningham]

For the last 5 (at least) years, the access MVP's have been saying to create the .mde file using
1. The lowest common denominator version of access that your users have.
2. On the OS that your users have.

 

[FuzMic]

Thanks Jeanette for the sharing which makes me dig into Late and Early Binding and also compare the difference between ! & . notation to reference objects in the hope to find an answer.

You are probably right: .mde created using even the lowest version of Access within Win of higher denomination than the final users will cause problems. Thus so far i have not been successful in creating .mde with Access.02 in OS of Vista or Win7 to allow users with xpWin to run it. Is this the FINAL?

 

[Jeanette Cunningham]

I believe that Win7 comes with a free virtual machine setup with the Winxp OS. I read this recently from a well-respected mvp - Albert Kallal. I must admit that I have not tried this, but it might help you.

Also have a look at this
http://allenbrowne.com/bug-17.html

 

[FuzMic]

Jeanette I am already using vmware with xpwin as virtual machine; that's the way to go to create .mde within win7, you are right again. Cheers!