>Hi all,
>
>I'm using 5.0 and have two grids on a tab in a pageframe. One grid is used for entry and the other is used to display a name and code (also exists in the entry grid) so as the user moves through the entry one they can see the code and name for what they are on (there are many columns). Previously I tried splitting one grid with very sloppy results so decided to try the two-grid alternative. What's happening is that the display grid is not staying current with the entry grid. If the user moves (via click, scroll, down-arrow) to a record below the bottom one (end of what's seen, not end of file), the display grid just keeps displaying the same batch of records from the view (first record and down) and doesn't scroll. Do I need to capture each action the user does on the entry grid and perform it on the display grid? Is there a better to handle this? I'm on a contract so development time is even more of a priority than usual.
>
>Thanks! Renoir

Sometime ago there was another thread on this subject. The only way I've ever worked around it was to make grid1's recordsource a view which is parameterized by the record on the form. Grid2 can then be linked to grid1 and it stays in sync quite well. Grid1 can do a =requery() of the view of the record on the form changes.

Steve