>>>Greetings!
>>>
>>>I want to make my VFP5 EXEs available on a LAN. Is there a way to copy certain support files to each PC in lieu of going through a setup process for each application on each PC? In other words, which files are necessary to run a VFP5 EXE, taking into account any special library files it may be using? With good ol' Visual Basic 3.0, all one need to do was copy VBRUN300.DLL to the Windows system directory (in the simplest scenario). I doubt it's that easy with FoxPro but, still, is there a way?
>>>
>>>Thanks!
>>>
>>>Michael Reynolds
>>
>>Michael, you could do similar thing in VFP 3.0, copying VFP300.ESL to \WINDOWS\SYSTEM, but not for VFP 5.0. What you need to do - use a Setup Wizard - it has an option for network setup. You put your setup files on the server and just run it from each workstation.
>>
>>Nick
>
>Thanks for writing, Nick.
>
>Actually, I wanted to know if it were possible to avoid running the network setup. What I hope to do instead is have something like a batch file that could be run from each workstation, causing the necessary files to be automatically copied to the proper locations.
>
>You see, I don't want the application itself installed on the PC. The application and data will reside on the server. I only want the files needed to support the application to be installed on the PC. Therefore, I hope to indentify which files are needed on the PC in order to run a VFP EXE on a server.
>
>Thanks!
>
>Michael Reynolds


If your application resides in the server, you can also place your VFP500.dll and VFP5ENU.dll into the same directory to make it run. As John Harvey said, if you have some library files that need registering, you will need to register into each PC.