Your thoughts are appreciated but why is browse for better than set filter? and how would you write a locate that is equivalent to GO TOP?

>I can not see what causes your problem, but I have a few advices:
>1. Avoid SET FILTER whenever possible, instead you can use "BROWSE FOR yourcondition"
>2. Don't use GO TOP after SET FILTER, instead use LOCATE which in many cases is extremely much faster
>
>>I have been having trouble lately with a browse command causing a shift in the current work area. For example:
>>
>>

>>set filter to PermID == lcPermID and (LoCWW > 7 or HiCWW > 7 or LoCWWHrs > 24 or HiCWWHrs > 24)
>>go top
>>if ! eof()
>>	messagebox("The following records need to be corrected for CWW > 7 or CWWHrs > 24. ")
>>	browse && shows table1
>>endif
>>set filter to
>>
>>brow title 'Get ready'   && shows table2
>>set filter to PermID == lcPermID and upper(valid) = "NO"
>>go top
>>

>>I can't imagine what's causing this unless my installation has become corrupted somehow. Has anyone else ever experienced this? This is happening throughout my application in various routines and prg's.