Cannot locate the Microsoft Visual Foxpro Support Library

[HarryStottle]

Created an installshield setup.exe with the vfp9 runtime option selected and the merge module default destination. The runtime files are installed in the default destination directory (\program files\common files\merge modules) and they're all there (vfp9renu.dll,vfp9r.dll,vfp9t.dll)

But when I run the app, it produces the "Cannot locate the Microsoft Visual Foxpro Support Library".

So I've tried copying the runtime files to the application install directory, the windows system32 folder and the windows system folder. Doesn't make a blind bit of difference.

Am I missing a trick here? Do the files need explicit registration? Are there other files I need to include or what?

 

[Mike Lewis]

Harry,

Yes, these files do need explicity registration (or, at least, vfp9r.dll does). However, the InstallShield setup should have done that for you.

I'm not sure what you mean by selecting the "merge module default destination". The folder you mentioned is where InstallShield finds the MMs on the developer's machine. On the user's system, they should get installed in "C:\Program Files\Common Files\Microsoft Shared\VFP". However, I don't think that affects whether or not they get registered.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

My sites:
Visual FoxPro (www.ml-consult.demon.co.uk)
Crystal Reports (www.ml-crystal.com)

 

[Mike Gagnon]

(vfp9renu.dll,vfp9r.dll,vfp9t.dll)

I see you might be missing 2 of them. msvcr71.dll (needs to be registered )and gdiplus.dll (depending on what kind of graphics you are using).
But the msvcr71.dll is the major one needed.

http://fox.wikis.com/wc.dll?Wiki~VFP9RuntimeFiles~VFP

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.
ReFox XI (www.mcrgsoftware.com)

 

[HarryStottle]

Thanks to both, but no nearer a solution. The two files I didn't mention are indeed required and are automatically selected if you select VFP9 runtime files in installshield. The reference to the merge files destination is an option in installshield version 5 freebie that comes with vfp9. (Right click on the selected module and select properties, then you get an option to determine where they will be installed.) Generally I don't touch that and leave the defaults but I did, on this occasion, try to amend the destination from the default (C:\Program Files\Common Files\Microsoft Shared\VFP)
just to see if that made any difference. It didn't.

And all relevant entries are present and correct in the registry.

So, we know its not missing files. We know its not a path problem. We know its not a registry problem. And I know I've used this sodding program before without this behaviour so I'm guessing that I've done something stupid at my end but I'm banging my head against the wall trying to think of possibilities.

 

[Mike Gagnon]

Reboot?

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.
ReFox XI (www.mcrgsoftware.com)

 

[HarryStottle]

OK, the problem has morphed. What I've discovered is that the reason its whingeing about not being able to find the support library is because its looking for vfp8 runtime files.

It is, of course, easy enough to include those but that's not the real issue. What I want to know is why - given that I've recompiled the application in vfp9 - why is something inside it still demanding vfp8 stuff and how can I find the guilty components?