>>>I'd like my grid to be fairly large on the page but when the user double clicks on it, for it to get smaller and reveal fields for changing the values (the grid is NOT the right place in this instance).
>>
>>There are several ways to accomplish this. If there are only 2 ways that you want the grid displayed (rather than a dynamically configurable grid for the user), then I would consider:
>>1) use two grids on the form (one or the other always invisible)
>>2) use 2 grid classes that you can dynamically add to/remove from the form with addobject/removeobject.
>>3) Forget the switching-grid approach and use a pageframe instead. When the user hits the right button on page1, programmatically activate and refresh page2, which can hold the smaller grid and the detail information. This would be my favored approach.
>
>Thanks Mark, I'd go for #3 myself but the user wants it all on one page. A bit of a tricky one. I think I'll probably just make the fields as squashed as possible and the grid as large.
>- Sarah :->
Most useful attribute in addressing your resizing problem is the COLUMNS ( be sure to include the terminal 'S' ). You can generically reference your grid columns with something like:

with thisform.Mygrid

for j = 1 to .columncount

if .columns[j].name = "Goodone"
.columns[j].width = nGoodWidth
else
.columns[j].width = 0
endif

next j

endwith

You would want some other condition clause on the 'IF' to properly discriminate the good / bad columns for your purposes.