Ummm, implying - no. Stating - yes. ;-)
If the actual executable is running on the remote workstation and using local Windows resources on that workstation. This is as opposed to, say, Terminal Services or Remote Desktop where you are using server Windows and, basically, pushing screen IO out to the remote.
>Are you implying that even though my development workstation has VFP7 installed that this is not sufficient to run a VFP7 executable from a remote workstation?
>
>>Hi Joe,
>>
>>Can't find VFP7RENU.DLL, which is the resource file. The EXE has to be able to find this file and VFP7R.DLL.
>>
>>You can always create a mini-Setup using InstallShield Express - Limited VFP Edition which comes with VFP7 and specify the VFP7 Runtimes and VC++ Runtimes as the merge modules. Then run this setup on your workstation and, viola, it works!
>>
>>
>>>I get this error on my development work station when attempting to launch an EXE created in VFP7 which is located on a network work station (by double clicking on the file in Windows Explorer).
>>>
>>>I CAN launch a copy of the same EXE which is located in a folder on my development work station.
>>>
>>>Does anyone know what's going on here? I've never experienced this bhavior in earlier VFP versions.
>>>
>>>Thanks in advance.
>>>
>>>Joe McLaughlin
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05