-- Verify the error does not happen when REPORTBEHAVIOR=80
It does not happen with REPORTBEHAVIOR=80 only REPORTBEHAVIOR=90

--Instead of previewing, try printing (to Fax or MS Document thingy) to see if the error still occurs.
Yes. It happens when printing also. I thought it was just in preview

-- Expand the Xsource folder and recompile ReportPreview, ReportOutput with the debug flag on so that you get more information on where the error is occurring.
-- Open the debug window with a watch on Program(), line() etc to get more info on where the error is occurring

I was wrong about ReportPreview.app. The error happens in ReportOutput.app
As I said it only happens the second and any subsequent times I try to print or preview.
I can ignore the error and continue and everything works fine and it only happens in development so this is not that big of a deal to me. But if it is a bug in ReportOutput, it would be nice to get it fixed.
Also if I'm doing something or have something set up wrong I'd like to know about it.

Here is where it fails.

ReportOutput .app
FrxOutput.prg
Line Number 237
OUTPUTAPP_REFVAR.ADD(oTemp,cType)


Now what? Any ideas?







>Robert -
>
> I'm working with a very simple report. When in design mode I select Preview I'm getting a Program Error, "The specified Key already exists. This is error 2062. When I first preview the report I don't get the error, but on any subsequent previews the error occurs. I can't imagine anything is wrong in the report, because it is so simple. It must be something in ReportPreview.app. Do you have any suggestions?
>
>I remember something like this happening during the beta.
>
>Here are some ideas for tracking this down, off the top of my head:
>
>-- Verify the error does not happen when REPORTBEHAVIOR=80
>
>-- Instead of previewing, try printing (to Fax or MS Document thingy) to see if the error still occurs.
>
>-- Expand the Xsource folder and recompile ReportPreview, ReportOutput with the debug flag on so that you get more information on where the error is occurring.
>
>-- Open the debug window with a watch on Program(), line() etc to get more info on where the error is occurring.
>
>- Colin