The Citrix thing is another issue alltogether. For now I'd be happy if the path thing worked on a simple networked Pc.
>I have absolutely no experience with Citrix, but I guess it has something like a PATH statement which you could set so that also your VfpCommon directory is searched?
>
>>I think not. At least, as it is now, I have nothing on the local machine, everything on the servers & Citrix.
>>
>>I want to simplify this - not complicate it - further by having a VfpCommon dir with all the common stuff in one place on the network.
>>
>>>Then I suggest that you crate a "loader" program which
>>>1. Checks whether the necessary files are located in the defined directory on the local machine
>>>2. If not, copies the newer files from the server to the defined local directory
>>>3. Starts the EXE from the local machine
>>>
>>>
>>>>Yes, me too, but that's exactly what I'd like to avoid. As the number of apps grows, this is not a very satisfying solution.
>>>>
>>>>---
>>>>>Place the runtime files in the same directory as your EXE, no registration is required! I have done it for years, works wothout any problem.
>>>>>
>>>>>>We've got a number of VFP apps running off our network servers & Citrix.
>>>>>>
>>>>>>Rather than copying the VFP runtime stuff to each .exe / dir, a potential maintenance nightmare, I'd like to place it all in a VfpCommon dir.
>>>>>>
>>>>>>Our support people have tried all sorts of stuff with the path & even registering the .dll's. So far with no luck, so they've given up.
>>>>>>
>>>>>>Can not locate VFP support library, it says.
>>>>>>
>>>>>>Why would that be? And what should I tell them to do?
>>>>>>
>>>>>>
>>>>>>TIA & BR
Peter Pirker
Whosoever shall not fall by the sword or by famine, shall fall by pestilence, so why bother shaving?
(Woody Allen)