Hi Colin,

I'm fairly confident that there is no printer information in our FRXs. We use Doug Hennig's class library (that was made available in a FoxTalk issue a while back) to create our FRXs on-the-fly. In examining the resulting FRX, I don't see any printer info in any of the fields.

We've narrowed down the problem to the CREATE REPORT command. It is executed to create the FRX structure after which its contents are removed and replaced with our own (on-the-fly stuff). This command is taking a longer to complete in VFP9 than it was in VFP6. On some machines it took two minutes; on others it took seconds (but still longer than before). Our solution now is to have an empty FRX available and avoid creating it using the CREATE REPORT.


Mike


>Mike -
>
>We do not put any printer environment information into our "built up" FRXs. The reports could vary from a single page to several pages. The issue does not seem to depend on this factor. REPORTBEHAVIOR is set to 80 (the default for VFP9).
>
>Hmm. In that case, I'm out of immediate ideas. I don't know why this configuration would be slower, if what you say is true. Are you *sure* there's no printer configuration? How do you create your FRXs on-the-fly?
>
>- Colin