>
>I had the same problem, but it was caused by the number of controls not grids. My load time was cut by about 75% (or sped up 400%) when I created a class for my pageframes. Each page other than page1 is made into a subclass by selecting the entire page (ctrl-A) and doing Save As/Class. Then blank out each page and put code in the activate event of the individual pages of the pageframe to build the page. This will build the page when you need it, not when the pageframe loads. The down side is each page will come up a little slower the first time you look at it. I learned to do this from the VFP Developers Guide version 5 or 6, in the Chapter for Optimizing Applications, Heading Optimizing Forms and Controls, subheading Dynamically Loading Page Controls on a Page Frame. Specifically page 405 in my version 5 guide. I think this is the way to go, especially if your users won't always look at the pages with the grids on them.
>hth,
>Marcus.

That's the answer I was looking for...I had read about this problem somewhere before, but couldn't remember where, and was hoping someone here might point me in the right direction.. I appreciate it... I didn't believe the SQL was the problem...the queries are pretty simple...the amount of controls/controlsources on the pages are quite numerous...it sounds right on the money..I'll give the subclass idea a shot. Thanks again

sc