>>>>>A client is running a simple vfp3 app on a very simple windows 95 peer to peer network. One computer on the network will not run the application from a shortcut but will run it from Windows Explorer (by selecting the server's drive, clicking on the app's folder, and then double clicking on the app's exe.) We can right-click and drag the apps exe out of the explorer onto the desktop and create a shortcut and the app will not run. It complains of all sorts of things like "class not defined" or "can't add object to grid". All the other computers on the network have exactly the same setup and they run just fine.
>>

Make sure that the Starts In entry in the shortcut is set properly. Also, under VFP3, UNC support is not complete - use a mapped drive letter to make you life easier.

>>>>Are you sure the client has (all) the (most-recent) VFP runtime files? Are there any external (.ini) files that need to be on the client? Any special directories (for .tmp storage, etc)?
>>
>>>Thanks for your reply...No ini fils are involved. All the computers on the network are using the same version of the vfp3 runntime stuff. To my knowledge, only one version of the runtime module exists. All the data resides in a sub-folder of the apps native folder on the server. All other computers on the net are able to get to that sub-folder. I can't immagine that this one computer (identical to the others as far as make and processor etc.) would be having a difficult time accessing the sub-folder. This is really a strange one.
>>>
>>>jd
>>
>>Well, that's sort of the point. *Something* is different about this machine - the question is 'what is it?'. Has the application *ever* run on this machine? Does the application look for data via an absolute (vs relative) path? Can you copy the application to this (faulty) machine and run it?
>
>If I open the windows explorer, locate the folder on the server where the exe resides and double click on the exe, the app runs just fine.
>
>jd