Good suggestions.

I am running VFP 6.0 and doing dataentry from a 16 page application. There is a lot of information to gather from the application, about 750 distinct items in fact :-)

Aren't pages in pageframes containers? Should I disable textboxes on pages that aren't visible?

It also takes forever for the program to start and end. That's kinda a pain too, but I can deal with it. When someone sits down to do data entry, that is all they are going to be doing for a few hours. A ten minute startup or shutdown isn't so bad then.

My custom textbox is kinda cool. It does two things, one is it reads a speerate table for a validation rule, and the other thing is that it generates a second textbox that is used for validation purposes (the data entry person sets it to S if the data is suspect, then a manager reviews the suspect fields.)


>>I have a form with about 750 text boxes (of my own design). The form is very slow. I think the problem is the number of objects, since the form became twice as slow when I added a couple of grids on one of the pages.
>>
>>I make use of LOCKSCREEN alot, and I've analyzed my code to kill unnecessary lines of code, macro expansions and stuff like that.
>>
>>So anyway, what the point, right? The point is that the data entry form is slow to use. Slow to tab from field to field, slow to cut and paste, slow to switch pages, slow to do anything. Is this normal? Is it because I have so many objects within one form? Should I make each page of the data entry form a seperate VFP form, instead of using page frames?
>
>Without moralizing too much on your pageframe being too "busy," which it does appear to be :)
>You didn't say what whether it's vfp5 or 6. As Garrett said, there's a slowness bug in 6, especially for refreshing pages and grids. Whether in 5 or 6, have you run the Coverage Log/Profiler? That's a big help in rooting out the slow code...