I have found one consistent place where VFP6 is slower than VFP5. Fortunately, it is a correctable problem.

The issue is with pageframes. In VFP5 pageframe refreshes we very fast. So I wrote base classes that refreshed all of the pages in a pageframe when the pageframe or it's underlying form were refreshed - say in a maintenance form when the record pointer changed.

In VFP6 refreshing of page frames is slow. What's more, the speed of the refresh is directly proportional (big surprise) to the number of controls total that are in all pages of the pageframe.

I also was getting outrageous screen instantiation times with forms that were very quick under VFP5.

The way I corrected it was to rewrite my pageframe class to only refresh pages on demand, when they were accessed. It took a little bit of trickery because I didn't want to have to subclass at the page level because I'd lose design-time capabilities. This, however, did solve the performance problem.

If this is your problem I can provide some code examples if necessary.

Hope this helps.

>Hi Jamie -
>
>You're not gonna like this answer, but....
>I've seen the same thing (and am forced to stay w/VFP 5 for now). The strange thing w/mine was that the refresh times didn't really seem to be affected, but the time it took just to tab between controls(even tho it wasn't actually running any code), and for some of my textboxes it's like I'm "typing in mud". I can type 4 or 5 letters before they start to appear on the screen.
>
>Also see Mac Rubel's article in the Feb '99 issue of FoxPro Advisor.
>
>I keep hoping someone will come up with a simple explanation....
>Good Luck -
> ~ellen
>
>>I've just upgraded from 5.0 to 6.0 and upon loading a Client form notice the lapse from click to view is 8 - 10 times slower than 5.0. I'm using a 233 Mhz w/32MB RAM. Any simple explanation for this??? Thanks in advance.