>Maybe you could try to isolate the problem by doing a test with a simple grid and just a textbox and a label in one column. If this works, you could put a container around the textbox and label, put the code to resize the container in and check again.

Yep, I built this whole thing in a separate test form originally. Looks like I'm going to have to go backwards a bit.

BTW: Are you aware, that changing the height of the active row by resizing a control in there will change the height of all rows? This might not look very well, when the user walks through the grid. How about determining the maximum height of the text for all rows before loading the data in the grid:
>


Yes, I am. I resize everything from the inside out, so the user can never see more than one row at a time. Basically, without writing a book here, the container, grid and rows are originally only as high as the txtScreenDesc, which is above the lblScreenLongDesc in the container itself. When they click on the lblPlusMinus, everything (including the grid height and rowheight) expands based on the height of the txtScreenDesc + ScreenLongDesc + 5. It worked nicely with the scrolling editbox, but now I think it's getting to be more trouble than it's worth...


- Brian