Hi Dana,

You should consider building report execution wrapper class,
which will set report behaiviour to 80 or 90 accordingly.

While 95% of reports can be still succesfully built and run by old RE (80) there will be cases where you will need some of new features (multiple detail bands,HTML etc) so you should not just dismiss VFP9 reporting as unusable, but try to incorporate it in your reporting framework, in a such way that can pay you something back for your investment.

By using exclusively 80 or 90 you will do some trade off, eighter speed
or new features. By using them interchangeably you can get best of both worlds.

2c


>Thanks, Colin. We always remove printer information from the report. We've been doing that for years. I understand about paying a price. But this price seems to high. They've paid a lot of attention to speeding development, but it's not worth it at the cost of runtime sluggishness.
>
>Dana
>
>>Dana -
>>
>>In addition to what the others have said, make sure you are not saving the printer environment information with the report.
>>
>>VFP9 differs from VFP8 in that it referencs some newer printing DLLs in Windows (VFP8 uses some that were deprecated long ago!) and these have a tendency to hit the network looking for network printers when they really don't need to. Removing the printer driver information from the FRX can sometimes make a difference.
>>
>>As for new features vs speed, well, I think every programmer understands that you can't get something for nothing.
>>
>>- Colin