I know I will need to change many of reports if I want to use the new engine. I do like that I can set the ReportBehavior on and off but I am unlikely to have some reports with the new style and some with the old. I think the dual-interface of the toolbars would annoy my users.

The thing I find strange about the *s is that is on this report I am working with it only happens if the field is not calculated. If I add a SUM() calc in the field properties it diplays fine, all other properties remain the same. It look like a Bug to me.


>Patrick,
>
>>I have been looking into how the new VFP report writing generates my existing reports. I notice a lot of my reports will end up with ******** in place of my data.
>
>The new-style reporting uses GDI+ instead of GDI to render the reports and because of that (I'm oversimplifying a bit) many existing reports will need to tweaked a bit under VFP 9 in new-style mode. This is a known effect and is noted in the release notes, I believe.
>
>Since you have the SET REPORTBEHAVIOR 80 command at your disposal, you can bracket some reports with that, setting back to 90 after the report run, while setting 90 to the overall default for your app. That way, you can run those reports in 90 mode that have no spacing problems and can gradually adjust the others with overflow or line-spacing problems.