>Another option would be to build a temporary SQL Cursor before you run the report, that way, you can SELECT ... WHERE and only have records in the cursor you are going to print.

That´s a grat idea, but i´ll have use the sys(2015) function in order to create a unique name for the cursor i create, then modify the report's dataenvironment so it open the cursor i created then, after the report is printed, delete the file i created.... tricky eh?

Thanks a lot.