>I have a VFP 7 application installed at several sites. Fatal Error/C0000005 errors are occuring frequently and always on the following line of code:
>

>REPORT FORM (filename) TO PRINTER PROMPT PREVIEW
>

>
>There are now close to 50 reports in the application. Users have reported the problem with many of the reports and I have seen the problem myself on many reports. I can't say for sure that ALL the reports have been affected, but I've seen it occur on a number of different types of reports from the simplest listings to reports where I hack the frx before running.
>
>The problem does not occur every time a report is run. Sometimes it will happen the first time a user attempts to run a report and sometimes not until the third or fourth time. Usually when the user logs back in to the application and tries again immediately, the report will run but sometimes they're thrown out again.
>
>I have tried to run a series of reports repeatedly in the same sequence with the same parameters. Eventually I always get the Fatal Error, but never on the same report in the same sequence.
>
>All the reports have had printer-specific info removed from the frx. I have replaced all non-TrueType fonts with TrueType and limited them to Arial, Courier New and Times New Roman.
>
>In addition, I have tried the following without success:
> Setting my default printer to Generic/Text Only
> Deleting the resource file, making it read only, and turning off resource file altogether in application
> Moving the application to VFP 8 (based on "Fatal Exception on Report Preview in Visual FoxPro 7.0" from List of Memory Exception Bugs Fixed in VFP8)
> Disabling write cache on the hard drive
>
>In VFP7, the error message is:
> The instruction at "0x00706a68" referenced memory at... (varies)
>In VFP8, the error message is:
> The instruction at "0x007a775f" referenced memory at... (varies)
>
>The first part of the message is always the same (within VFP version), no matter which report I was attempting to run when the problem occurred. This doesn't mean a lot to me, but perhaps it will to someone who knows more of the inner workings.
>
>I can't think of anything else to try. My users' patience is wearing thin and mine isn't far behind. Any suggestions will be welcomed.
>
Laura,

While I haven't run into this issue (I don't use the PROMPT clause), I do have a work around. I've never seen this error occur without the PROMPT clause. It would seem to me that this is the underlying problem. The workaround is to design your own form, if possible, to handle the output.

Second, I'd suggest that you log this bug (if you already haven't) on the MS web site. Give them as much information as you can, including VFP version and Service Pack, and the same for Windows.

Third, either post a message to, or email John Koziol, asking him to look at this thread (give him the thread number). John is a friend of mine, and, if I know him as well as I think I do, he'll ask you for code to reproduce the problem. If you can give it to him, I'm sure that he'll see to it that it gets looked at.