I really see no difference in the approach. In cases of going through Termnal Server or accessing the workstation through some remoting application like GoToMyPc, PC Anywhere or Remotely Anywhere, on your workstation you have the "window" into the remote computer. That window *is* your remote computer. Only the path that is working on that remote computer will be relevant.

>Thanks for the reply. I may be confusing TS issues w/ possibly unrelated GoToMyPC issues. The TS-connected user would be running the EXE by being directly connected to the server (?), where the GoToMyPC user may be connected to the workstation instead. Regardless, everyone still runs the launcher to start. Do you see any mapping / reference problems with the following as a remote & non-remote user:
>
>A non-remote, workstation user runs the app launcher. For first-time users, the launcher doesnt find the EXE and asks the user to locate it. A getdir saves the selected folder (using UNC notation) into a local INI or DBF on the workstation, copies down the EXE, and then runs the EXE.
>
>>>Are there any issues using application launchers on workstations to start VFP apps when run remotely via terminal server or GoToMyPC (citrix)? Would a stored drive/path value (using UNC notation) on a workstation pointing to the location of a VFP database on a server still be valid to the remotely connected user?
>>
>>Hi Chris,
>>
>>I have several VFP apps installed under Terminal Services and they worked through the Launcher apps. That works the following way:
>>
>>I used the network data locations mapped to the drive letters. The EXE is located in the user's share on the Terminal Server (accessible as M: drive). Since the application remotely accessed through Terminal Services really runs on a Terminal Server, only drive mappings/UNC path used on a Terminal Server matters for the access. The remote application will not see any drive/path value that are set up on the user workstation.
>>
>>i.e.
>>
>>The data and the current version of the EXE are stored somewhere on remote network.
>>
>>On that same remote network there is a Terminal Server that has the drive letters mapped to the location of the application data and the location of the EXE (could be the same mapped drive) Say, they are mapped to drive G:
>>
>>The user has the application set up on the Terminal Server on his M: drive (that is really user's personal share on the Terminal Server.
>>
>>The Launcher checks for the presence of the new EXE on the drive G: and if the EXE was updated, copies it from Drive G: onto the drive M: and starts it from drive M:
>>UNC path can be used here, but all the path are relative to the Terminal server, not the user's workstation.