>Hi Al
>
>...snipped great summary...
>
>>- Is a high-quality, low-latency network in place? It should be 100Mbit Ethernet or better, over Cat5e or better cable and with quality switchgear. For reliable operation, VFP apps should never be run over a wireless (e.g. WiFi) network connection. Ideally, VFP apps should be on a local area network (LAN), and not be run over office-to-office links (e.g. VPN or true private network over MAN or WAN).
>
>IMHO the "safest" way (seen mostly from possible network failure points) is runniung via TS or Citrix, making data access local seen from HW point of view, of the application "server based" as it is running on the server and only a thin client application shows the screen in the remote area. Especially when VPN security has to be added to the loop.
>
>Clearly not an option on the file server used here<g>, so irrelevant to this particular problem. I wanted to add that point as your info makes a great check list of options available, which can be used almost everywhere problems crop up.

Hi Thomas,

Thanks for the kind words. I fully agree that if you want to remove possible network infrastructure problems from the equation, then a TS/Citrix-type solution is the way to go. If everything is on one high-performance server then there is no network traffic generated by VFP itself, everything is local to the server box. The only network traffic is that to-and-from the remote client - and that traffic is efficient and fault-tolerant, specifically designed to work well on "iffy" networks - low bandwidth, high latency.

Isn't it amazing how much this model looks like the old mainframe/terminals environment? < g >

Do I recall correctly that you work in environments with various "big iron"? Have you encountered any i-Series or AS/400?