>>>I don't want to scare you, but just one thing from my own experience. I saw couple times VFP app working on workstation w/out Setup process applied, and producing unexpected crashes on seemingly accidental basis. The idea is that avoiding normal Setup, you just take chances.
>>
>>Now that you mention it, I recall this happening in the past as well. I'll do some serious testing on this to make sure. It's not a big deal to me if I do use the setup wizard, but I was hoping to simplify things if at all possible. I actually have one of the users PC's in my office, so I can beat it up pretty good. But, of course, the user always finds a way...
>>
>>Thanks for the help.
>
>John,
>In addition to Ed's comments, if your program needs MSGraph, an OCX, DLL or similar file the Setup disks will register it correctly on the new computer. This will save you LOTS of trouble-shooting.
>
>We have a network setup, which installs a small file into c:\temp, but also installs the basic default VFP files in the correct spots. It takes no more time to run than copying big files over from the network, can be run on multiple machines and sites, and reduces Tech.Support. You might try this approach, John.

Barbara, PMBI here, but this issue puzzles me also. I do a full install/setup of the EXE on one (PTP) network machine. For my Workstation-Only installations the setup wizard is configured to contain only my config.fpw file (to the app dir). Within the wizard I select all necessary (runtime + odbc, etc) files and the distribution disks are created. I then install on the workstations. This seems to work fine - or am I missing something? Thanks!