>I've got it solved by setting the recordsource of the underlying grid to "" (not the same recordsource as the report uses), then running the report and serring up the grid again. Later I'll try, if this will also happen with the foxypreviewer.

Or, better, just try to select the same records into a different alias on which the report will run, so the grid dancing (its refresh can have such nasty side effects) doesn't influence the cursor for the report.

And dancing is probably the right expression (just because I read the title as "data dancing when..."). The grid, when refreshing, would bring the recno() of the alias to where its current record is; your report is going through the same records and then the grid is jumping it back to wherever it needs to - with the net effect that you don't know whether the report is finished by that time, whether it started from the first record etc etc. Keep them separate.