>Luis,
>I could be wrong, but I don't see how you can hope to have the record pointer *not* move during a table update. Before you issue your table update, you could store the record number of the record pointer and then reset the pointer when you're done.
>
>>Hello everybody,
>>When you are using table buffering, that is, buffering=5 or
>>buffering =3, after updating several records and doing a
>>TableUpdate(.t.), the cursor is moved to the last record
>>mdified, I want the cursor to stay where it is without hav
>>having to doit manually.
Thanks for your answer, Nancy,
I save my record before updating, I am not appending, so my
record number is always a positive number, after I update I
do a GO RECORD m.nOldRecord, then I TABLEUPDATE() and that is
when the pointer moves, I though that TABLEUPDATE() was suppose to
move the pointer only when a problem was found, this according to
the Help file in Fox, but, I still need to save the record before
TABLEUPDATE() and move the pointer after that, but you are still
right, I should use the key in the index rather than the record
number.
=THIS.Thankx("for your help")
Luis Guzman, MCP
"The only glory most of us have to hope for
is the glory of being normal." Katherine Fulleton Gerould