A2007 mde deemed "Not a valid Win 32 Application"

[GraeagleBill]

I recently installed an app developed in A2003 on a Win 7 Home Prem system. I got the message "Not a valid Win 32 Application" when I attempted to launch the A2003 created mde "front-end". I then installed the front-end source mdb, which opened normally, and created a new mde file from A2007 but still get the message with that mde file as well.

I have several apps developed in A2003 that execute perfectly in A2007, A2010 and A2013, so I'm at a loss as to what the problem might be.



Any ideas as to what might be causing the failure?

Bill

[RuralGuy]

If memory serves, only ac2003 can create a valid ac2003 MDE. It sounds like you did it in ac2007 so I could be off base here.

[GraeagleBill]

I started with a mde file created in A2003 but it was deemed invalid when I attempted to open it in an A2007 runtime environment.

[GraeagleBill]

Could it be that the "back-end" mdb needs a "Repair and Compress"?

[GraeagleBill]

Could it be that the "back-end" mdb needs a "Repair and Compress"?

[GraeagleBill]

Could it be that the "back-end" mdb needs a "Repair and Compress"?

NO, that didn't make any difference.

I installed a different app and I get the same message when I attempt to open its mde, which is also a A2003 developed app. It's source mdb opens without error.

All I can think of is a corrupted A2007 installation.

[RuralGuy]

Any chance you've still got ac2003 around?

[RuralGuy]

Here's a link you may find useful: http://www.utteraccess.com/wiki/inde...nd_ACCDE_Files

[RuralGuy]

Hmm...It does say "* Access 2007 has two native formats (ACC2002/2003 and ACC2007) so it can create MDE's for both." I'd still like to see it created in ac2003. I have ac2002 (XP) so maybe I could convert it for you.

[GraeagleBill]

I don't have access to the offending A2007 system today. Later today I do have access to another A2007 where I can install the A2003 mde app. I'll post back after I've had a chance to test the mde there.

[RuralGuy]

I'll be around. Good luck with the project.

[GraeagleBill]

Had an opportunity to test things on another A2007 system, which BTW had an already app I developed in A2003 that's never had an issue. I installed the mde file and opened it without any problems. I also installed the source mdb and recreated the mde from A2007 without any issues.

I have to conclude that the offending system has a corrupted Office 2007. I'm not sure when I'll have access to that system but will proceed to do a fresh install of Office and will post back after I've done that.

Bill

[RuralGuy]

Thanks for the update. Please keep us posted.

[GraeagleBill]

For sure. This caper really has my attention. If there are snakes in the grass, we all need to know where not to step

[GraeagleBill]

Finally! I had to do a fresh install of Office 2007 Pro to be rid of the problem. Once installed, both the apps installed on the troublesome machine as mde front-end files opened normally.

One note here of interest is that when I uninstalled Office 2007 Pro I noticed an "Office 2007 file validation add-on" app remained in the list of installed apps, one that I've never seen before. I uninstalled that app as well. I've since looked at other client Office 2007 systems and DO NOT see any "add-on" apps related to Office. Sorry I can't report whether that "add-on" had anything to do with the issue as initially posted here.

Thanks for all the thoughts,
Bill