Question Error when opening MDE (which includes Access97 runtime) in Office 2007

[mvanreek]

Hello.
I build an application for a client in Access97 and gave them the MDE version which includes the Access97-runtime (because they have an Office (2007) version without Access).
When they try to open the MDE-file, the get the error:

"You can not convert or activate a MDE file" (my translation of the original error, in Dutch:
"U kunt een MDE bestand niet converteren of activeren.")

When I tried to install it on a PC with Office-2010 Starter Ed. (which is without Access), it worked fine.
Could anyone explain me what is the reason for the error, and how to solve it? By the way: I can not convert the application from Access97 to a newer version (like Acces2007),because I only have the Access97-runtime, and because the client doesn't have Access, I have to include it in my installer-file.

 

[DCrake]

Do you have the Access 97 mdb file?

 

[mvanreek]

Yes, I do have the mdb-file

 

[mvanreek]

Do you have the Access 97 mdb file?

yes, i do have the MDB

 

[DCrake]

Try opening up the mdb and recreating them mde file again.

 

[mvanreek]

I already did (a complete recompile). But I don't understand why the MDE works on my PC (and of some friends PC's with similar configuracion as my client as), but not with the client

 

[DCrake]

If you are using Access 2007 and have the developer extensions then re package the mde with the correct Runtime instructions.

 

[mvanreek]

I have Access97 + SDK (toolkit) which includes the runtime, I dont have Access2007, neither does my client, he has Office-2007 Starter Ed. (which does not include Access)

 

[DCrake]

Then I think there is conflict between the two. Maybe running a A97 runtime version on a machine with Ofice 2007 on it, even though Access is not part of the install is causing the problems. Don't quote me but that is what it sounds like. Maybe someone else can either confirm or deny this.

 

[mvanreek]

But why does it work on a PC (Win-7, Office 2010-Starter, without Access) that is used for the deployment-test, which is similar to the PC of my client? Could it be a missing DLL of VBA?

 

[DCrake]

It could be a missing reference. What point is it erroring? The problem with mde's they only tell you an error has occurred, not what error it was. Have you got them to try the mdb version on their machine, at least you will be able to identify the actual error.

 

[gemma-the-husky]

I am not sure - I think maybe A2007 can't directly run a A97 MDE. and you need to convert it to a later version.

Alternatively - do they have windows 7 - I am sure that will not run A97 at all.

 

[mvanreek]

Thank you for you advice Dave and Gemma. I once tried to do a conversion to Access2000, but the automatic conversion of Access2000 gave me some errors, so I'm afraid it will be a lot of manual work. I read VBA of Ac.97 differs much from that of later versions, and my program has lots of VBA in it. And e.g. in Ac.97 you had to program you combo-boxes manually (with an event), while in later versions it is a standard control. But if I would do the conversion to Ac.2007, could you give me an estimation of how much time it would take?

 

[DCrake]

Work out how long it would take you to convert it in hours. Then multiply that by your hourly rate then add 20% this will be a base line work with. Then look at the lost opportunity whilst the application was undergoing redevelopment and add that cost into it.

When you have a figure that becomes your budget for someone else doing the work for you. However that person will be more knowledgeable in conversion and may pick up on things you didn't. At the end of the day you get the job done better and faster than you could and it also leaves you with the time to do what you are supposed to be doing.