>>>I have a simple form with a pageframe containing 2 pages. Page 1 has about 6 fields on it. Page 2 has a grid with the same fields set to read only. When I advance through the records on page 1 to the point where the scrollbars on the grid on page 2 would become active (the grid is now full) I get an overlay affect on page 1. The entire grid is not visible on page 1 but makes the fields jumbled. I do a page refresh after each advance of the record but nothing seems to help. I even tried to disable the grid but it still causes the same thing. Any ideas?

>>I had a similar experience, but in a much more complicated app. Try making the page2.grid1.visible =.t. in page2.activate, and page2.grid1.visible = .f. in page1.acitvate.
>>
>>Brenda

>I tried this but got the same results. Any other ideas? I've checked other similar forms and am finding this problem with them also. These are very simple forms used for maintenance of 1 table, I'm wondering if it may be a bug with VFP. I've also tried running one of the forms under VFP6.0 and got the same results.

All my suggestions seem a bit extreme, and illogical, but maybe you are at that point. These suggestions are off the top of my head and I have not tried any of them.

1. set grid.scrollbars = 0 (none) when on page1, and then reset scrollbars when on page2.
2. Could put your grid into a container and make the continer1.visible = .f.
3. set the grid.recordsource in the page2.activate and recordsource="" when you are not on page2. You will also have to set you headings, and column recordsources in page2.activate. basically you are setting up your grids data values each time you go to page2. you will lose any partitioning, column sizing, etc. (actually i have tried this one. have some special code that will save you partitioning, column sizing, etc. if this is important to you, and you end of using this one, let me know)
4. Could save your grid as a class. then "addobject" the grid to the page, then "removeobject" when you do not need it. you will add the grid each time. you will lose any partitioning, column sizing, etc.

just some crazy ideas. let me know what you come up with.

brenda