Hi!

OOPS, just not use set filter to. I guess VFP works the same way, but all these SET FILTEr's are used in background for each report when FOR is included in REPORT command. Because report is not waiting, filter got lost as soon as next command executed after REPORT FORM ... NOWAIT command, that temporary filter is dropped to make further executing of code consistent.

That could be considered not bug but just a limitation. However, indeed, this is rarely used and probably require a lot of effort from MS VFP team to fix this.

>Vlad,
>
>Do you test your suggestions ?
>
>NOWAIT clause causes REPORT command NOT to wait. So SET FILTER TO is
>executed immediately after REPORT command. Even report window preview shows two lines!
>You notice this easily if you run your changed progam.
>My users like modeless reports.
>
>
>>

>>
>>create cursor test ( test c(20) )
>>insert into test values ( 'line 1' )
>>insert into test values ( 'line 2' )
>>create report TEST from TEST
>><b>set filter to recno()=1</b>
>>report form test preview nowait
>><b>set filter to</b>
>>

>>
>>HTH.
>>
>>>I encountered the following bugs using REPORT FOR ... NOWAIT command.
>>>Those bugs are present in all Visual FoxPro versions.
>>>
>>>1. Clicking Print button in Preview windows causes GPF (VFP 5) or
>>>exception error (VFP 7)
>>>
>>>2. In test program, if I comment out the line
>>>
>>>create report TEST from TEST
>>>
>>>clicking print button prints TWO lines!
>>>
>>>Is it possible to fix this so that Print button uses FOR condition ?
>>>
>>>Test program:
>>>
>>>

>>>
>>>create cursor test ( test c(20) )
>>>insert into test values ( 'line 1' )
>>>insert into test values ( 'line 2' )
>>>create report TEST from TEST
>>>report form test preview for recno()=1 nowait
>>>
>>>