>
>I think Craig may remember my lamenting VFP's form refresh. Although exceptable on our standard P75/16 meg RAM workstations, the performance is less than lackluster on the WinFrame--the technology behind MS Hydra, aka Windows Terminal. The one test app does have a pageframe with a plethora of controls, so maybe it's a design issue...
>

I've had speed issues with pageframes. A lot of developers went nuts with one huge app page with n pageframes and n pages. These apps rarely run well in any environment.

>I do not want to code for database replication. I'd rather have something more like SQL Server's administration options. Guess I am lazy in that aspect.
>

Fair enough. I'm just trying to suggest that a coded solution may best fit your particular topology.

>As an aside, I would have to disagree with the notion that VFP 5.0 is such a leap from previous versions that it has driven off all the mediocre Fox programmers. With all the backward compatibility, there's nothing to stop someone from writing an app with @ ... SAY/GET to the screen with all the various READS, etc. We have one in production--dBase code recompiled under VFP. Not my idea, but he's the CEO's son...

OK, you can still do that stuff but I've never seen it. You can't use any of the power tools (with the exception of the menu and report builders maybe) without getting away from that because, after all, you no longer generate source-code SPR files like in 2.x. Counter-argument would be that you could still do cheezy QuickBasic style IO and coding in VB5 if you wanted too.