>when i do a full installation for a workstation (running windows across the network), it puts the win32s files in a local directory under c:\netwin, which they use as their local system directory. this is where the client wants all of these files (they have enough clutter on their network)

Dave,

Our client is also using a shared copy of Windows with a local system directory (c:\lanwin) containing .grp, .ini, and other user-specific files. When I installed VFP, it created a WIN32S directory under the network Windows directory. I still have to run a WIN32S installation at the individual workstations in order to allow them to run the VFP .EXE, but I think you need to have the WIN32S sub-directory under the shared Windows directory as well. Our VFP applications run fine using this configuration, so let me know if you would like any additional information on our setup.

Glenda Cherry
Computer Support Supervisor
DynCorp I&ET/EPA Telecomm
Washington, DC