>I thought that when a VFP's exe starts, it searchs for the VFP run-time in this sequence:
>1.- Same directory
>2.- Windows\system directory
>3.- Path variable
>Isn't it? Why don't the PC find it in the network?
>

Unfortunately, there's more needed than to just find the runtime; there are a number of registry entries needed to properly install VFP. The serarch path you mention is the default search path for .DLLs.

You must install the runtime on each workstation in order for VFP executables to run. If you insist, you can keep the runtime on a network drive, but there are performance issues with this, and if anything about their location changes, this can break VFP.

In addition to the requirements for the runtime files themselves, the runtime files are dependent on a number of other shared components, many of which must reside in the system directory. If the version of the file needed is not present on the individual system, or is not at least as current as the one the VFP runtime would install, VFP won't run. Some of these components are OLE-enabled, so theuy also must be registered.

Any ActiveX components also must be registered on each individual station.

Do yourslef a big facor and make a Setup Wizard disk set that at least puts the runtime and any ActiveX components needed on the local workstation; you can copy other files into place and handle creating the shortcuts and the like needed by hand or with another product.