>>Seems to be that RECORD clause ignores all Filter, Set Deleted and Set Key settings currently in effect, regardless of the command with which you use it. It would be interesting to try it with commands such as Delete, Replace, Recall, Report Form and any other command which has a scope clause. Not now, it's 2AM and I'm trying to read myself into sleep :).
>
>Hey wake up !!! :-) Ding ding ding...
>
>Feeling refreshed?

Sure do, thanks pal - the next night I sat until 3:30 without problem :)

>Yep, I'm sure you're right there. Another thing to keep in mind. Cheers for now.

Just ran a simple test - did a set filter to, made sure it didn't show any of the first ten records, then did a "replace TheBlankColumn with 3 record 2", and removed the filter - and sure the value was there. I think this was always so, by design - and it was always so, maybe as far back as the times when dBase III was peeing into the dust. Come to think of it, it does make sense - the filtering commands take action when you're moving the record pointer to the next record, or parsing multiple records based on another condition. With a Record n clause, you neglect all those conditions and go straight for that record, and it gets you there. IMO, not a bug, a not-so-well-known feature.

P.S. Sorry about 'pal', wrong dialect. Should have been 'mate', right?