>
>My initial posting I think, was that I had a pageframe object with 8 pages, three of which had grids..and that the addition of the seventh and eighth pages had significantly slowed the loading time...most of the responses were in connection with the grids though...I apologize if the posting was vague..sometimes it's difficult to convey the scope of the problem at hand. I do agree that the grids could definitely be part of the problem, but the SQL is extremely simple...it's just a SELECT into a cursor, and then a setting of the RECORDSOURCE to the cursor...the SQL is a simple (SELECT * FROM table WHERE table.PKID = MemvarID)..nothing more to it. I'm definitely always open to suggestions though, and I appreciate your input....
>
>sc
Sean,
For pageframes basic optimization is saving page contents as classes and in activate of pages :

if !type("this.myPage")="O"
  set classlib to (this.pageclassname) additive
  this.addobject("myPage",this.pageclassname)
  this.myPage.visible = .t.
endif

I would do timing with and w/o grids. Then if they take considerable time, copy each grid one by one to a new empty form and run. That would make revealing unacceptable grid load times easier. If grids are populated from an SQL, making recordsource directly that SQL string and recsourcetype = SQL is also worth to think of (does a slight gain). I'm sure you have indexes on PKID and deleted(). So this type of grid would load lightning fast.
Cetin