>Yor code is interesting, so could you be more especific, please....
>I mean, you´re telling me that is not good idea using report with filters...????

Nope, at least not with the PREVIEW clause. I tend to build cursors or use parameterized views for my reports based on VFP's Report Writer, avoiding the need for multiple tables in the report, command line filters and the like. For example, you could create a parameterized view based on the table using two parameters; if variables exist that match the parameter values associated with the view, they're used, otherwise, VFP pops a little dialog to prompt you for values. Build your report based on the parameterized view. Makes its own sauce...and the odds are, if I need a filtered view in a report, I probably need the same kind of filtered view elsewhere.