VFP app craches on startup

[EzLogic]

Client:
Windows Vista 64bit

App (few of them i tried to install for him)

compiled in vfp9 sp2
ran the setup using the install shield... mind you, this app is currently being used by 200+ clients and never had an issue.

i even tried a simple app (Hello there)

As soon as you click on the app/shortcut, i get the "microsoft visual foxpro has stoped responding" and then, when i hit cancel, i get the c0000005 error.

we tried on another machine, and it works well.. but, this app (his own machine) that he really needs the POS on is crashing.

i googled tons of it and i am clueless.

the embarrasing thing is he has other competition's POS and they work.. (not written in vfp)

what would you advise for me to do?

we ran virus scan, etc.. too.
virus?
hardware?
malware?
corrupt registry?

Ali Koumaiha
TeknoSoft Inc.
Michigan

 

[Dan Freeman]

Have you set up the app to run in XP emulation mode?

 

[EzLogic]

i just tried that with no luck.
also, tried it as "Run as admin"

Ali Koumaiha
TeknoSoft Inc.
Michigan

 

[EzLogic]

i also tried it without using Konxise... just the regular unshrunk version of the EXe

no luck

Ali Koumaiha
TeknoSoft Inc.
Michigan

 

[EzLogic]

i am sorry, this is on Windows 7 home edition 64bit. NOT vista.

i am running same version @ home and it works ... and my dev machine is win7 64bit. grrrrr

Ali Koumaiha
TeknoSoft Inc.
Michigan

 

[EzLogic]

ok, i just found out that he has couple apps (besides mine) that are vfp apps.

i noticed the vfp9ru.dll and others are different date/version than my vfp9 app.

mine was sp2.. i wonder if that's the culprit.. mismatch dll files????

Ali Koumaiha
TeknoSoft Inc.
Michigan

 

[Dan Freeman]

That'll cause it. Put YOUR runtime DLL files in the same directory as YOUR exe and they won't kill someone else's app.

 

[EzLogic]

Yep! Confirmed..

download it vfp9r.dll and vfp9renu.dll into my own folder and voila!

he had 2 other apps were in vfp.. kinda funny/cool though to see other apps written in vfp

Ali Koumaiha
TeknoSoft Inc.
Michigan

 

[Olaf Doschke]

Lesson learned. And actually that is what MS also recommends to avoid DLL conflicts (DLL hell): Put DLLs your app needs to your app and don't install into system32 or common files.

There are a few things you need to register, though, which means they are set to the same dll/exe for all apps.

Bye, Olaf.