>Hi,
> If I have a simple application that doesn't include ant OCX, HELP, WSH... just pure VFP 3.0 application, what runtime should be included? how large? Any article describe the usage of each runtime?
>

If it's compiled in VFP3, I don't know off the top of my head what's required. If it's VFP6, as noted, the VFP6R.DEP file outlines in detail the dependencies and file requirments for the runtime. The Setup Wizard does a good job of deciding what the required files are and budling them together.

As noted, there's a FAQ entry that runs through the files needed by VFP6 for the runtime distribution; you can take a look at that. As mentioned, there are registration requirements, both for self-registration and separate creation of the HKEY_CLASSES_ROOT nodes neded to link the VFP executable up when fired through something like the Explorer.

The individual functions are not isolable to specific files for the runtime; VFP is an interpreted language, and so the runtime represents an interpreter, not just a set of discrete runtime functions as is the case with compiled C code. You need all the runtime files.

Is there some problem with using a Setup Wizard install to put just the runtime in place? It gets the files installed properly on a cross-platform basis, and can be fired with little or no user interaction from another program using the command line switches (/Q has several options available to make the etup Wizard install nearly invisible within another application, and can generate a log file using the /G command line switch which you can parse yourself from another application.)

There is a sample setup for use with InstallShield Express written by Mike Helland here on UT as well, if you're using IS Express, you can use that script to build in the necessary install components to an IS Express installation. I haven't tried it, and still continue to recommend using Setup Wizard to drop in the runtime components, which is what I do with my own apps and InstallShield Pro.