>I would use two grids or use one grid and change columnorder of those two to >be always on left side.

I'm unable to use those solutions either. Reason being: The grid acutally has about 15 columns, so not all can be seen on the screen at once, it's more like 7. If I use two grids then the up & down scrollbars will keep the rows from matching, plus it would be a pain in the neck to get the last column of the first grid to setfocus to the first column of the second when the user hit tab. As far as using the columnorder and one grid, that's acutally what I'm doing now, but for somereason all the splitbar and partition junk does is simply DUPLICATE the entire grid on the two sides of the partition. In otherwords, if the user is on the left side of the partition and hits the tab key 15 times he bounces through every column, always staying on the LEFT side of the partition. This means that he can no longer see the first two columns, which the point of what I'm trying to accomplish. Now, if the user should happen to be on the RIGHT side of the partition, then it does work, except that the user can still see the duplicates of the first two columns on the right side as well, which makes the app look really stupid, and as I said it looks terrible because of the extra vertical scroll bar in the middle of the grid. If I try to change the width of the first two columns on the right side (or any other attributes for that matter) then the effects also take place on the left side, thus the problem with the SplitBar merely DUPLICACTING the table on both sides of the value in the Partition propery. There SURLY has to be some simple way to have a grid that the user can tab through 15 columns, only having seven visible at a time, and keep the first two on the screen at all times. AAAHHHHHH!!!!