Thanks, I agree, will try to follow these rules.

>Methods should be named with verb/noun combinations. The verb tells you what happens, the noun, what it works on. I also like the .Net practice of not abbreviating unless it's something very common like Html or Id. Take number for instance. Is it abbreviated Num or No. I've seen it both ways in the same app.
>
>So, following this guide, Tore's first suggestion is the best. Gregory's is good except that SavePosition doesn't tell you what position. Is it the position of the cursor on the screen? The record pointer? How you are sitting?
>
>
>>Hello,
>>
>>I am using a class which encapsulates most of the cursor handling in FoxPro. For example instead of GO TOP I say loCursor.GoTop() etc.
>>When I scan through a cursor very often I need to save the current position and after the scan move back to the previous record number in that cursor, which would look like this:
>>

>>LOCAL lnRecno
>>lnRecno = loCursor.Recno
>>loCursor.DoSelect()
>>SCAN
>>    *
>>ENDSCAN
>>loCursor.GoTo(lnRecno)
>>

>>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?