>>>>>Hello,
>>>>>
>>>>>I have created an application used the setup wizard to create the
>>>>>disk images. I have installed the application on a network and
>>>>>everything works great if I run it from the computer that I installed
>>>>>the application. However, If I run the program from another workstation
>>>>>I get the error that the Visual Foxpro Library can't be found.
>>>>>I tried to copy the vfp500.dll to the workstations \windows\system
>>>>>directory, but this didn't work either.
>>>>>
>>>>>Can anyone help me?
>>>>>Please email me.
>>>>>
>>>>>Thanks,
>>>>>
>>>>>Paul Acton
>>>>>pacton@ttsinc.com
>>>>
>>>>The normal way of distribution is to install locally (VFP application requires multiple dll/ocx, not only vfp500.dll).
>>>
>>>Hi Edward,
>>>
>>>Thanks for the reply...I'm not sure if I understand. I want to be
>>>able to run this application from many workstations. Do you mean I
>>>need to install the program locally on each machine? If I do this I
>>>will have a data subdirectory on each local machine. I guess I could
>>>then delete the local data subdirectories and add to the path the
>>>server's data subdirectory? This just doesn't sound like an efficent
>>>way to do this. Sorry to be so stupid about this...I'm new to the
>>>world of Visual Foxpro and Windows for that matter.
>>>
>>
>>Paul,
>>
>>I use Jerry's method. It is the easiest for updating the EXE when you make changes. Depending on your network, the speed price is should be minimal and only a delay when starting the app.
>
>There are many methods to run network applications. While it probably isn't the best way to do things, I have successfully deployed VFP5.0 applications on a network without any installations. The two files always necessary are VFP500.DLL and VFP5ENU.DLL. If you put those two files in the same directory as your EXE file, Users should be able to run the EXE over the network. Some users without newer software may get the error "VFP500.DLL is invalid or damaged" and for them, you need to update the OLEAUT32.DLL file in their WINDOWS\SYSTEM directory. (The error message is deceiving). I just put my OLEAUT32.DLL file out on the network and have them copy it down to their computer if they get that error. Note that if you use any ActiveX controls or ODBC drivers, there is no way to get around the install. Like I said, this isn't necessarily the best way but it works. If you put 10 EXE's out there in different directories, it is quite a disk space waste to have 10 different
>VFP500.DLL's out there.

It probably works just because 1. all your users have MS Office 2. you have 'plain' app (no Active-X, etc.).
Anyway, it's always better to stick to some proven standard way.