Once I was able to preview the report in a zoomable way (with your help, thanks), I moved on to presenting it at the right zoom level right away. This is useful since I have are several reports designed in small fonts to make them printable in a standard sheet.

I was following the example on how to use REPORT FORM myForm OBJECT loListener and got a message that the preview object was not properly configured. By tracing I meant compiling the ReportPreview.app from the source code and steping until ran into the error.

I *will* read the manual and work some more on this later today. :)

Thanks,

Alex



>I'm sorry, I don't really understand this. In what way is the ReportPreview incorrectly configured and what are you tracing through?
>
>Is this about your progress bar? That's not part of the ReportPreview at all <s>.
>
>I'd like to help find out why the progress bar is doing what it's doing, but we need to look in the right place. Tell me some more about your report:
>
>* -- what are its groups like
>
>* -- does it have multiple detail bands and target aliases (probably not)
>
>* -- is this report running off a different table (selected or driving alias and related to your cursor with the records)? Is there a one-to-many relationship set up, or more than one?
>
>Again, all this has been refined since your build, so I'd like to confirm whether you're seeing a scenario we have, or have not, improved.
>
>Look: whether or not you're writing a Preview, you do need to read at least the default.htm of the release notes to get started understanding the architecture. There are a number of different objects here.
>
>A couple of messages ago you were saying that you couldn't find reporting enhancements listed in the docs. You should at least be willing to read *one* HTML document to get oriented in VFP's report system (and, specifically, its runtime architecture) before wasting a lot of time <s>.
>
>
>>L<