Just curious, does it make a difference whether NODEFAULT is issued first or last in your IF...ENDIF? Also, if you trap (from the point of hitting enter and this point on) when the record number in the main table changes - when does it occur? Verify the value is correct and the record number when you press ENTER and then see when the record number changes in that table specifically. You do not have any relationship setup between the two tables in the dbc right?

as to the UG, we do not have one and since I do not know of any other VFP developers (other than those I worked with on Fort Bragg and those I work with now and NONE of them even visit forums online let alone attend a UG meeting) who would be interested, it doesn't look like a UG will occur here anytime soon.


>>Yes I have seen this too so I would be very interested in seeing the culprit when it is determined. To resolve it for myself, we store the record number in a form property and whenever focus returns to the grid's page we reposition the record pointer if it has changed.
>
>At present, my testing is showing this: After speed searching for the desired part on the List tab, if I press Enter the following code executes:
>
>

>if nKeyCode = gnEnter
>	thisform.LastListCol = this.parent
>	thisform.pgfParts.ActivePage = 1
>	nodefault
>endif
>

>
>If, instead of hitting Enter, I simply click on the main tab to activate it, the form works as expected (when moving back to the List tab the correct record is displayed - the same one as is displayed on the main tab). So what in that code could cause this issue? Still investigating . . .
>
>Was it you that was starting the UG up there? How's it going?
>
>Russell