>>>You can use REPORT FORM FileName1 | ? [ENVIRONMENT] [Scope]
>>> [FOR lExpression1] [WHILE lExpression2] (provide your filter in FOR expression) or don't use local variables in FILTER condition or pre-select your data into the cursor (my favorite approach).
>>
>>Yeah, already selected into cursor and made that work. I'm to the point where I really hate the report writer. They wrote some cool stuff like the dynamics, but what we really could have used was some basic functionality improvements.
>
>You might also try using a PRIVATE variable in the routine that calls your report form. It won't go out of scope like the LOCAL will. I have several static variables passed to reports with this method.

Using PRIVATE in that way is every bit as bad as using PUBLIC variables. Macro sub is THE answer if he's going to use SET FILTER.