The first time this happened, I thought it was by chance... Now that it's happened again, I'm wondering if I'm experiencing operator error, or if it's something more.

I have a number of reports attached to my database.  I've been working with my Bookings report this morning, have tweaked it, and it has given me my HTML report perfectly, no problem.  I just went back into designer to change a header, and when I opened the report, all of the LE's turned into Unbound Value boxes, and a number of them were completely black.  Nothing would work.  The crazy thing is, the report worked, literally, 5 minutes before.

This happened again, before, on a different report.  I ended up  having to redo it.  Any ideas on why this might be happening?  Am I doing something wrong?

Thanks,
miss_doo

Miss_Doo,

I know that I tracked this down and fixed it (will be in the next release) but, for some reason, I don't have a note on what the cause was. I do recall that it required a fairly complex combination of conditions to produce the problem.

One thing that may help to avoid it is to close the Report Design Tab before running the report in Preview Mode. I think it had something to do with a combination of an open tab, a LE bound to a Money field and some formatting selections, possibly involving programming. Whew!

This has happened to me several times, I have learned to always save the dsr to a new db, test to make sure it works correctly, if alls o.k. then reconcile, its also helps to test the programming in the editor, most the time its a problem with a programming statement I forgot to test, or a reference to a LE I deleted and forgot about.

Erika,

Quote:

I just experienced this problem of value boxes going black. And yes, I did have the design tab open when I launched preview mode to test the report. Four simple lines of programming, but no money fields at all in the app.

Is there any way to recover this report, or do I have to completely rebuild it and delete the original?

Hi Ray,

FYI, it just happened again with the design tab CLOSED.

BTW, if any of you folks can reliably reproduce this problem (meaning make it happen on purpose), I'd really like to know what the steps are so I can make absolutely sure we've taken care of this one. I believe I've fixed it, but it was always intermittent so it's hard to be certain.