>>>>>>I have to change my code, before SCAN, so that the SCAN would go through all records. Therefore, I will need to SET ORDER TO before the SCAN.
>>>>>>What is a better practice, saving TAG() to the memory variable and then restoring it (by SET ORDER TO TAG(cSavedTag)).
>>>>>>Or, saving the ORDER() to the memory variable and then restoring it (by SET ORDER TO (cSavedOrder)
>>>>>>?
>>>>>
>>>>>I personally use ORDER(), but if I want the record marker to stay then I use SELECT .... and scan result cursor.
>>>>
>>>>As I mentioned to Antonio, this is a Cursor Adapter cursor and I don't want to break something in the process of updating it.
>>>>So saving the ORDER() and restoring it works for me. I actually tried the method of saving the TAG() and restoring and it works too. I don't know what is and didn't see the difference.
>>>
>>>I can't remember who said that if you can't do something in VFP with at least 3 different ways you can't do it at all :-)
>>
>>I used to hate that fact, but recent recent JS is worse. It already had lots of weird stuff, but syntactic sugar additons and small enhancements adding to mental burden make vfp a clean language in comparison ;-)
>
>Imagine if you add Fuzzy logic (i.e. behaves like Fuzzy -- cat of one of my friends)...

You probably already have seen the "Wat" video about JS and Ruby ;-))
(if not, Google will find it. Nice 10min if you had a face-palm recently)