>>>>I'm getting a "filtered cleared" message as I'm generating a report on a filtered table. Is there a way to track down what is causing this?
>>>
>>>

>>>procedure one
>>>LOCAL lcFilter
>>>
>>>lcFilter="0"
>>>SET FILTER TO anyfield=lcFilter // using LOCAL variable in FILTER or SET KEY... 
>>>do two
>>>
>>>procedure two
>>>*SKIP 1 && cause "filtered cleared"
>>>REPORT FORM anyreport && cause "filtered cleared"
>>>

>>>
>>>MartinaJ
>>
>>Great, so you can't generate filtered reports?
>
>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.