>Ernie,
>
>I no longer have FPW on any machine so I can't do any testing. I see you are using an LJ4. What happens if you try using the LJIII drivers instead? Video drivers can also be at fault for printing GPFs.
>
>>First, I'm using Fox 2.6a running Windows 2000 Professional on a Dell 8100 with 256MB RAM, CPU chipspeed of 1.4GHZ, 90 GIG HD, printing to a network printer that's an HP Laserjet4 Plus.

I didn't try switching drivers because all along, the program and single report worked just fine. It was when I added that second report that the problem started. I guess I could have tried, but I was determined to make sure it wasn't something I did or a problem in the code. Which it was, but the behavior wasn't documented.

In a prior thread Ed Rauch (sp) wrote up a lot about HP -vs- MS print drivers and about 4 years ago, with another 2.6 and VFP5 application, we went around and around swapping drivers to no avail. (I suspect the problem back then was similar to the problem this time around -- separate reports trying to share memory variable names.) When I have a moment, I may try to recreate all of this just to prove the point to myself again. But right now, I'm tired and it ain't billable so I'm off to the next Fox hunt.

Ciao.