Runtime files for Foxpro8

[paulthibodaux]

Which runtime dll's must be installed on a users machine for Foxpro8?

 

[alvechurchdata]

This works for me - all in the same folder as the VFP exe:

vfp8r.dll
vfp8t.dll
vfp8renu.dll - this is for the English distribution

All these are in c:\Program Files\Common Files\Microsoft Shared\vfp\.

You'll also need:

msvcr70.dll from the Windows System32 folder
GDIPlus.dll from the same folder as vfp8r.dll

If you're using XML you'll also need these three from System32:

msxml4.dll
msxml4a.dll
msxml4r.dll

Geoff Franklin

http://www.alvechurchdata.co.uk

 

[Mike Gagnon]

Please pay attention to the files that need to be registered (although it might still work if you do not register them - it makes for a bad setup that may cause problem in the futur and you might realise that not registering the files is the issue)

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

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[craigber]

Better solution...use an installer program, like InstallShield Express that ships with VFP 7+.

Craig Berntson
MCSD, Visual FoxPro MVP,

http://www.craigberntson.com

Author, CrysDev: A Developer's Guide to Integrating Crystal Reports"

 

[alvechurchdata]

use an installer program, like InstallShield Express that ships with VFP 7+.

InstallShield's good for commercial distribution - it gives the user a good first impression and reassures them that they've done right to buy my system.

On the other hand, InstallShield is hard work if all you need is to get the exe running on another PC. I like the way that I can just copy a handful of files into one folder and have the system running.

I've never had to register any of the DLLs yet - perhaps I've just been lucky.

Geoff Franklin

http://www.alvechurchdata.co.uk

 

[Mike Gagnon]

I've never had to register any of the DLLs yet - perhaps I've just been lucky.

Take a look at the quote in faq184-2644. It was made by someone (Ed Rauh) that knew what he was talking about. Unfortunately he passed away. But I would also question the fact that when you first install FoxPro itself on a fresh computer, the product itself registers these runtime files. This would indicate to me that they need to be registered, otherwise Microsoft would not register them. And when you used the setup Wizard (VFP6.0), it too registered the required runtime files. With InstallShield now you have to included them AND specify the ones to be registered. This is all well documented since VFP3.0.

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[foxdbs]

vfp8r.dll
vfp8renu.dll - this is for the English distribution

vfp8t.dll is replacement of vfp8r.dll for multi-threaded dll, so usualy this file isn't necessary.

 

[craigber]

mgagnon...

Are you sure about that? If you select the proper merge modules, doesn't it already know what needs to be registered?

Craig Berntson
MCSD, Visual FoxPro MVP,

http://www.craigberntson.com

Author, CrysDev: A Developer's Guide to Integrating Crystal Reports"

 

[Mike Gagnon]

Craig

Are you sure about that? If you select the proper merge modules, doesn't it already know what needs to be registered?

AND specify the ones to be registered.

Sorry to be misleading, the statement applied more for DLL's that are not part of VFP, like home-grown DLLs. You are correct in saying that InstallShield knows what to do with the VFP merge modules.

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[wgcs]

This would indicate to me that they need to be registered, otherwise Microsoft would not register them. And when you used the setup Wizard (VFP6.0), it too registered the required runtime files

Whether they need to be registered or not, I think is not so obvious as whether you program runs or not. VFP can be an ActiveX automation server (which absolutely MUST be registered to work), but I expect it is rarely used that way by a distributed Application.... So some features are probably simply not available if the DLLs don't get properly registered.

- Bill

Get the best answers to your questions -- See FAQ481-4875.

 

[Mike Gagnon]

Bill

My understand (I cannot find the reference anymore) is an unregistered runtime file from foxpro (assume this is multiuser evironment), will be instanciated differently if they are registred than if they are not. If I recall is unregistered they re-instanciate them themselves over and over, rather than using the same instance (which could spell trouble). At least that is what I recall from the article I read.


Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.