Retrieving VFP runtime DLL name required by EXE or DLL

VFP stores in an EXE/DLL information about what runtime DLL is required to run it.

This is sample code. Add error handling and adjust to your requirements as necessary.

? VfpVersionFromExeOrDll("C:\Program Files\My Company\MyVfpApplication.exe")
? VfpVersionFromExeOrDll("X:\Somefolder\MyVfpDll.dll")

Appropriate license for this class not found error at runtime

Code that runs fine in development may generate Appropriate license for this class not found (OLE error code 0x80040112) at run-time.

There are two types of licenses for ActiveX controls - development and run-time. See INFO: OLE Control Licensing in Visual FoxPro for more information.

VFP 9.0 Versions

VFP 9.0 version information for service packs and hotfixes.

VFP 9.0 Report Features in Runtime

In order to deploy VFP 9.0 object-assisted report features in runtime, the REPORT*.APP files have to be distributed with your application and their location stored into _REPORT* system variables.
The error 'Variable _REPORTOUTPUT is not found' may be generated if they are not populated properly.

How to pass parameters to VFP EXE

Passing command-line parameters from Windows to VFP created EXE is different from passing parameters to VFP programs or functions in VFP application:

  • All parameters are passed to EXE as strings
  • Parameters should not be enclosed in single quotes because quotes will be treated as part of parameter
  • Parameters with spaces can be enclosed in double quotes
  • Parameters are separated by spaces not commas
Subscribe to RSS - runtime
_REPORT* system variables
File System Variable Notes