Hi Ivan,

If you can isolate the problem form/pageframes/grids and some small samples of data that will repro this behaviour, zip it up, send it to me, and I will take a look for you.

Best

-=Gary


>Hi friend.
>
>>So, from what you are saying, the PKs are being auto-assigned by Codemine right?
>
>Not really, this one table is not a parent of any other. I don't have Codemine assigning PK automatically to it.
>
>
>>OK. So you are saying that even if you don't add a new record, if you edit the last row in the grid and then click Save, the record pointer jumps to the first position/row in the grid?
>
>Yes, you're completely right.
>
>
>>If so, let's forget the New record for the time being and see what is actually happening in the grid.
>If you click into the last row in the grid, everything is OK until you click Save after editing the data in the grid. Am I assuming correctly here?
>
>Yes, you're reading my mind.
>
>I did all the Step ON stuff and got the record number changing inside the cursor.cmdataacess.update , in the following line :
>
>

>        GO m.nThisRec IN (THIS.cWorkarea)
>

>
>I noticed that this method runs 3 times, in the 3rd the record point was moved.
>
>To carry on with life, I put some code inside the New toolbar button for that grid and I move the record point back to the "new" record. But I still have the problem when they just change something in an specific row, and then save it ... wich makes the record point run back to the first row.
>
>Funny stuff.
>
>Best.