>In one instance, issueing a TableUpdate moves the record pointer. Does anyone have a clue why this world happen or what can be done to prevent this behiver? What I am doing now is:
>
>CurrRec = recno()
>=tableupdate(1, .T., "TableName")
>goto CurrRec
>
>This works but, this application has around 500 tableupdate calls. It's a big job to do Microsoft's work for them.

That's a bad habit to get into - if you append a record, it's going to have a negative record number before the TABLEUPDATE(), and a positive one afterwards; use a primary key and a seek instead to avoid errors.