If you use table buffering instead of row buffering, then moving the record pointer won't inadvertently save anything. The inadvertent save is the main reason I avoid row buffering.

>I have a 1-1 relation set between 2 tables, and fields from both tables mounted on a form. The relation is set as so:
>
>

>use hours in 0 order wcode
>use main in 0 order wcode
>select hours
>set relation to wcode into main
>

>
>Fields from table main are informational, with the text boxes set as not enabled. When a user adds a new record in the hours table, the first thing that happens is that they must enter a work code. I would like the relation to take effect and show the corresponding information from table main. As it is, you have to move off the record and come back to get the information to show up. Refreshing the form does no good unless you move the record pointer and return to the record. These tables are set up with buffering, and in the middle of a new add, I don't want anything inadvertently being saved, which will happen if the record pointer is moved.
>
>Any help is appreciated