>>>>I do something like this without trouble using a table (should work same for views)...I just do a grid setfocus in the each page activate, so long as table is selected. The second grid automatically scrolls to show the selected record...
>>>
>>>Thanks Bruce, but (there's always a "but" isn't there), what if the user scrolled past the active cell so it is no longer visible? Then the setfocus in the activate event simply moves the user back to the record she's on. Also, if a user scrolls down several rows, then chooses the third visible row on the grid, how can I make the other grid shows the active row in the same relative position?
>>>
>>>I know -- I ask a lot :)
>>>
>>>Singing the "I had a great idea, but it turned out really ugly" blues,
>>>Valerie
>>
>>I know what you mean (s)...here's what I do for this: since it's not easy to capture the current record/grid row without clicking on a grid column, I move from one grid to the other with a click on grid object. That is, the user clicks on a grid record on one page, then the code opens the other page to the same place. I use a non-editable ID column with special text color and underline to indicate "more info is available"...
>>
>>None of my design-phase users have requested the feature you're trying to build so far (and I won't bring it up, either (s)). But if someone comes up with a direct solution, I'm interested too...
>
>I have feeling that it should be one grid 'containing' all columns but showing either first or second set of them. It can be done by resetting Column.ControlSources on fly. So basically, we shouldn't have pageframe design. It should be one grid and some button/checkbox which will trigger column.controlsources back and forth.

You could certainly do that, but it's some extra work setting column widths, inputmasks, alignment, etc...but actually I have more non-grid objects/fields on my pages also, so I would have more trouble...but Valerie might look into your suggestion...