>Ed, PMFJI but I have a client who is looking at Citrix. What are the problems involved with using VFP with Citrix? Is it very complicated? Is thin client worth it ro should they just be looking at a "normal" network? I know this is slightly off the original thread and I can repost in a new thread if you think it is better. Any time you can give in answering these questions would be greatly appreciated. TIA

The biggest problem with VFP apps under Citrix is speed; screen update time is poor, and refreshing a single control requires refreshing the entire active window because of how VFP controls and windows work. It does work, but whether the speed of screen update is acceptable is going to depend heavily onb how busy your forms are and the speed of your connection.

Thin client is worth it in many cases; an n-tier approach to development, with a front-end that uses standard Windows controls is probably the best course of action. VB with the right choice of widgets is probably a better front-end choice than VFP; VB with non-compliant widgets is just as bad as VFP. InterDev has worked well for me in the experiments I've done. I have yet to actually put an InterDev-based front-end solution in place in a production environment for a client, although I have a couple of pilot projects going that seem to be working well.

>
>>This is much the same issue as the problems with using VFP in a thin client environment (eg with Citrix or WTS) - VFP's controls are not real Windows controls, and VFP forms and Windows do not behave in the same fashion as other WinAPI Windows.
>>