Hi Terry,

I have no problem with the addition of a line like go top or locate as it can make reading the code later more undestandable and in most cases the performance impact would not be that great. However, many purists will argue that each estraneous line of code and especially one that causes additional moving of record pointers is inefficient and should be avoided whenever more efficient means are available such as the scope operator in the replace command.

Elmer

>Righto, Elmer.
>
>I still think it's best to stick to what you know'll work, rather than rely on the exceptions tho'. Besides, what extra effort is it to go top or locate? If you take a look at the next reply to my comment, some "lazies" miss out the ALL. Where do you draw the line? I think it best if Mohammed sticks to basics, no?
>
>:-)
>
>Terry
>
>>>Pleas note also that your originalcode should not have worked because you need to move the file pointer after a "Set Filter", ususally by "Go Top", before you do you table searches, updates. etc. on the filtered data.
>>
>>Hi Terry,
>>
>>Moving the record pointer is taken care of by the ALL scope in the replace commands specified.