>I am wracking my brains out on this. I have created a report which has field properties based on a cursor which is created on the fly (ie, c_example.shipqty). The code is roughly as follows:
>
>If something is true
> go do a few things
> give a message to the user
> select the cursor for the report
> give another message with ok, cancel option
> if ok is selected
> report form repexample noconsole to printer prompt
>
>EndIf
>
>Here's what happens. If I set the code to preview instead of print, the preview looks totally correct. But if I click the print button in the preview window, it prints the report out with a page of 0s (there should be 2 different detail lines). When it's set to print instead of preview, it either prints out the first detail line multiple times and ignores all other detail lines, or it prints out a page of 0s. If I put the set step on, I can clearly see that the necessary cursor is there and contains the correct data. With the set step on, it prints out exactly as it should. I have re-written the code, and re-named and re-created the report. Nothing works.
>
>I have 5 other situations in my app where I'm doing basically the same thing, and it works fine in all those instances. I have had 4 other programmers look at this, and no one can figure it out.
>
>If anyone has a clue about what I might try next, I would sure appreciate it!
>(I have also tried using a wait window, but that didn't work either.)

Are you using a REPORT ... FOR condition? I believe that a preview/print can cause problems with that.