When I try to install the application on the server, I get a message about long file names can't be supported on the network. I want to install the app on the network server & run it from the workstations. I assume you mean the exe & the data on the server. Is that correct?

>>>
>>>You can build a Setup Wizard install to place jsut the runtime and controls on the target systems, and then create a separate install application that creates shortcuts to the network.
>>
>>How do I do this? By target systems, I assume you mean the workstations. What goes into the workstation install & what goes into the network install?
>
>There are two ways to run a VFP application with a network present:
>1) Install the application on a network server and run it from the client computers, or
>2) Place the installation files on the network server and install the application (from the network) on each client computer.
>
>There are certain files that need to be on the client machine either way you do this. They are called the runtime files. A list of them can be found in the VFP help (there are only 3 or 4, or so).
>
>If you want to follow plan 1, install the application on the server (in a place where everyone who needs it can get to it).
>Then install the runtime files on each client computer. It may or may not be obvious that you can create an application to do this as well.
>
>If you want to follow plan 2, place the files created by the VFP Setup Wizard on the server (where everyone who needs them can get to them) then install the application on each client computer.
>
>Take heart; either way, it's easier than (or as easy as) it sounds.
>
>Some .OCX files may need to be installed on the client machines as well (if you're using 3rd party ActiveX controls, as mentioned in the first paragraph above). These can be included in whichever installation method you choose.
>
>Good luck, and keep at it!