>Hi all
>
>I have just installed an application (my first MM app) at a client who is running NT server and has 4 NT workstations. The app is on the server. Root directory for the app on the server contains the .exe and .ini files as well as other required files, data subdirectory contains all the data files.
>
>The workstations do not have the server mapped as the same drive letter. The app only works when the .ini file local drive entry drive letter matches the drive letter of the mapped server drive on the workstation.
>
>Changing all the workstations to have have the server mapped to the same drive letter is one solution and will take some doing. Any other suggestions??? or workarounds????

Is there a reason why you need to store the EXE and INI on the server? When I install an application I always store the EXE and INI locally on each workstation. That way I can modify the INI settings to customize each workstation. In addition, the application will run faster because ther is less network traffic. The data is still stored on the server. I am assuming you are using VFP tables, if not then I would also store the DBC on each workstation.

To handle the problem of keeping each workstation current with the lastest version of the software, I compile my application into an APP file. Then I create a very small wrap-around EXE file for the purpose of checking to make sure the local APP file is the lastest. If not then it will copy from the server the lastest version. I also use the EXE to make sure the workstation has the lastest DBC files if they are stored locally. In addition, I also map drives if they are not already mapped. The last thing it does is call the APP file which runs the application.

This apprach works great and is seamless for the end user. When I have an application update I only need to copy it to one location on the server and the next time the user goes into the application it will self update on their workstation.

Hope this information is useful.