>My V.F.P. 3.0b MULTI-USER approved PROJECT, developed on a Windows 3.11 system. . .
>The Problem: I was told that I could COPY the VFP300.ESL from the C:\Windows\System to the Network location (V:\VFPAPPS\TOOLS) and each new user could directly use the PROJECT. Not True!
>I have seen that it is possible to place a PROJECT (like the V-FoxPro-App ABRA) executable on the network and any PC allowed network access can run it - furthermore - the user should not be required an identical network mapping path of V:\VFPAPPS\TOOLS! (We might want to Map them F: or G:)! Some PC’s are WINDOWS’95 and some are WINDOWS 3.11 Workgroups; therefore, TWO sets of setup diskettes are created. Currently, when a new user is assigned duty to the PROJECT, I must use the setup diskettes on the user’s PC (later I delete the PC - TOOL subdirectory). We call this “FOXING the PC” machine. I do not want to “FOX” 100 PC’s. WHAT IS THE PROPER WAY TO “SETUP” MY NEW USERS TO THE PROJECT?

I put the .exe on the network machine and put the .ESL with it and it does work fine.
To solve the drive path issue, I get the user path dynamicly for each user.

Mo