Yeah, I had been kind of hoping to convert all reports over to VFP 9 behavior, but was not aware that the speed difference could be so noticeable. I had run across the problem of text being wider and some reports had started displaying asterisks. So it seems obvious that you have to weigh the advantages and disadvantages for each report and change the behavior as appropriate. Thanks for the reply.

>Hi Russell.
>
>>I was wanting to change a system over to ReportBehavior 90, but the report I was working on took 30 seconds to generate, whereas before it was nearly instantaneous.
>
>As Dorin pointed out, one big change in object-assisted reporting is that all pages are rendered before the first one is previewed, as opposed to the old engine, which previews the first page immediately but doesn't render the next page until you move to the next page. There are pros and cons to the new approach. The major con is that it takes longer before the first page appears. The pros are that pagination is much faster now (try running a several hundred page report under both systems and clicking on the Last Page button, then on the Previous Page button -- under the old engine, it was painful but it's instantaneous under the new one), UDFs only fire as pages are rendered, not every time the user moves back and forth between pages (long-running or resource-intensive UDFs could cause problems with the old engine), and calculations can be done more reliably.
>
>So, like most things in VFP (and life), there are tradeoffs. We heard the same complaints when Windows came out -- Windows apps were slower than the DOS versions they replaced. At least you have a choice now, so take your pick -- better performance or better rendering and more powerful features. You don't even have to decide that globally; you can do it on a report-by-report basis.
>
>Doug