>There appears to be some misunderstanding as to my problem.
>
>The left and right panes do indeed stay in sync. My problem is this:
>
>Starting at the top, cursor down the laft hand pane one at a time. The right hand also moves down. When the cursor reaches the bottom in the right hand pane, the next cursor down, the cursor is no longer visible in the right. Therefore this record can not be seen
>
>PS I cannot use grid because there are 50 converted programs with this code in them.
>
>My refresh is 1 second also.
>
>Any further comments.

I haven't succeeded doing anything much with your problem. I tried adding a Valid or When function to your browse clause, but most of the time it complained that "No update tables are specified. Use the Tables property of the cursor.", obviously thinking we're having a view and not a cursor.

Anyway, the problems arise only when you come to the first right-invisible record while sitting on the first column of the left pane. If you move down the second column (or move TO the second column while the record on the right pane is invisible), the right pane scrolls just fine.

This works, but it uses an OKL on the DownArrow key like this:

On key label DnArrow do refr
Browse Fields ;
cTest,;
cTest2 ;
Partition 36;
REdit ;
LPartition ;
Title "Help me"
On key label DnArrow

proc refr
skip
keyb "{tab}" plain
keyb "{tab}" plain

Beats all the sense out of me why it didn't work with 'keyb "{tab}{tab}" plain' - it never accepted the second tab until I made this two commands. Anyway, I've used two ugly beasts here (OKL and Keyb), but they are in a suitable company (Browse), so the aesthetic rules are not much violated ;>.

I've made my machine slow (playing .mp3 music) and it's just a 100MHz AMD, so the additional refreshes this causes may not look so annoying on your machine. The trouble with Browse is that it's as clumsy and unpredictable as Grid :), and you don't have too many doors for the repair man to come in thorugh. This fires anytime on DownArrow, and not only when you need it.