Mike

Thanks for that, I already have a launcher in place for the executable, so it wouldn't be too much work to include the DLL. Just wanted someone elses opinion to clarify that.

Thanks
Kev

>Hi Kevin
>
>IMO, I would not do that. They're called networks because they are not gross productivity. When you need to get somewhere quickly, do you jump on the subway or grab your own car? It's a matter of balance. An army of CPUs and harddrives can outperform a single CPU and its hard drives.
>
>I worked for a company that installed their software that way. The CFO got really annoyed when the server went down once. The DLLs could not be found when the server went down. If the DLLs were local, the users could have saved their files to their PC hard drives, at least until the server came back online.
>
>Think of your server as a single file cabinet. If every file in the entire company were stored there and every person had to go there for files, there'd be huge traffic jams. If the server goes down, certain functions may be unavailable to VFP on the PC.
>
>Share the data because you have to. Install your app(s) and VFP (and it's DLLs) on the local machines. This is the best balance.
>
>Look into application launchers to simplify upgrading your apps on the local PCs.
>
>You can't really upgrade VFP7 to VFP8 by replacing the shared dlls. So, this really gains you nothing in either the long or short term.
>
>>Hi
>>
>>Is it OK for me to place a VFP DLL onto a network share and have N/W PC's using the DLL at the same time?
>>
>>Thanks
>>Kev