>Do you have grids on the form? Make sure, the focus is not on the grid while running the report.
>

Thanks Nadia !

I could not understand why a report that was suppossed to be 1 page was coming out many many pages.... And it would NEVER do this in the debugger.... The report was printed from a method called in the init of a form that had been called from the dblClick method of a grid. The cursor before the report was the expected one... But the cursor after the report was not expected ? And the biggest kicker is that this cursor is not the cursor bound ot the grid !

I resolved this issue by calling the same method in the activate of the form insteado of the init hoping like you said to remove focus from the grid before printing the report..... This works !

Thanks !! ...... I have been pulling my hair out over this one !

Greg



>>I have a report that changes cusrors in the middle of the report. The correct cursor is Selected and then a Go Top is issued. Then, I have a messagebox popup to tell me the Alias() before the report starts and another on for after the report is exited. These return different aliases. When the report begins, it gets enough records from the correct cursor to make two pages. In the statusbar, I can see that the wrong cursor is already active. I can click on the toolbar to move to the second page and that does fine, although there should be 3 more pages. When I click on the toolbar to go back one page, the report is "reconstructed" from the wrong cursor, which contains only two records and now the report is only 1 page in length.
>>
>>Does anyone have any idea how this is possible? What can I do to debug and find where this cursor is changing?
>>
>>I hope I have clearly described my problem, but if not let me know and I will try to explain further.
>>
>>
>>Thanks in advance for any help!
>>
>>Don