>Thanks for your help, George.
>
>I don't know if you read the whole thread, but at Marcia's suggestion I removed the TO PRINTER PROMPT clauses so I was left with:
>

>REPORT FORM (filename) PREVIEW
>

>and still saw the problem, so I don't think it's the PROMPT clause.
>
>I've sent the report from the Microsoft dialog many times from each of the different VFP versions and Windows versions. (Each time I click the "Send Report" button I like to imagine the server at the other end screaming, "Duck! Here it comes again!". Gotta do something to keep a sense of humor about it.<s>) I'll try logging it manually as well.
>
>I hesitate to bother John yet, only because I can't lay out steps to reliably reproduce the error. I'm not sure if I could extract a reasonable subset of pieces to send him. But that does give me an idea of a couple of steps I might take to narrow things down. By doing so I may be assemble a subset. If I can do that I'll write to John.
>
>Thanks again for all your suggestions!

Laura,

I happen to know a little about how Microsoft does its testing. They understand that what may happen one time may not be applicable all the time.

Things like memory leaks fall into this category. If you provide as much information as you can (including things like the version of Windows, the version of VFP, drivers installed, what was running when the problem occurred) they'll appreciate it.

As far as my old buddy John Koziol is concerned, he once said, "Love them bugs." So don't hesitate to email him directly with as much information as you can provide. Afterall, anyone in this business who says that, deserves what he gets.:-)