>>I find this a little bit cumbersome, so it would be best to have two methods, one to save the original position and the other to move back to the original position. But I am at a loss how to name those methods, everything I can come up with ("SaveRecordNumber", "MoveBackToRecordNumber") do not sound anything intuitive. Anybody has a bright idea how to name those methods?
>
>A better practice is to instantiate an object that remembers the record number. When destroyed (if by release method or simply going out of scope) it resets the record number.

In theory I agree wholehartedly, but as object creation in vfp is comparatively [to C# for instance] slow and setting records also is needed sometimes directly inside loops this is one operation I leave just to bare vfp - it is one of the strengths and should not be burdened with method call or creation overhead. Of course YMMV as always...