we are going to try it. we'll let you know


>If you have some machines that are the same, or similar, maybe you could try one with a local installation, and see how that compares to the network option.
>
>And let us know :)
>
>>thanks Al. I think that the network meets all the requirements you mentioned - so I will go ahead and try it
>>
>>
>>>>I am now involved in the maintenance of a VFP app with 40 users on the network. The exe is stored on the network share.
>>>>Currently vfp6 runtime files are stored locally. The application needs to be recompiled in VFP9. From a distribution standpoint it would be much easier to put the vfp9 dlls in the application folder on the network, rather than rolling out to every machine. Are there any downsides to this, e.g. performance, or something else?
>>>
>>>The performance hit might not be too bad, or even noticeable as long as:
>>>
>>>- the network is gigabit or faster, configured properly (DNS etc.) and not too congested
>>>- the workstations have lots of free RAM so they can cache the runtime files after being loaded the first time
>>>
>>>Other possible considerations:
>>>
>>>- depending on what your code does, runtime files might need to be registered on a workstation, which might require a local installation
>>>- for fault tolerance it might be better to have the runtime local. For example, a local EXE with local runtime could check for the expected presence of network drives or shares and give the user useful troubleshooting information if they're not available. If the runtime is on the network, it may not be available, so your app won't run at all - users will get an unhelpful "cannot start Visual FoxPro" message