--
I switched to VFP 7 and did a Type To Print GetAKey.PRG successfully to check out the current printer. Than I switched to a different default shared printer and tried Modify Report again and got the error again. Taken together these facts seem to contra-indicate the bad printer driver theory.
---

I don't believe Sergey said that it was a "bad printer driver". However VFP 9 and VFP 7 use printer drivers for reports quite differently (you must have noticed the different printer setup dialog). And, FWIW, the Report Builder calls on some of the new capabilities that VFP 9 natively also requires. We know for a fact that there are some printer drivers that may behave well under some circumstances but have minor errors that VFP 7 wouldn't notice but VFP 9 would.

In early versions of Fox we had the same type of questions about video drivers. People would say "it's Fox's fault, my other programs work fine!" and we'd have to explain that, in fact, Fox stresses the video system and drivers particularly hard, calling on capabilities that other programs may not require <s>.

So please tell us (1) what the printer driver you are using is. Also, (2) do you see the same thing with every report? (3) Do you see the same thing with reports that have their printer environmented saved and those that do not? (4) If you pick a different default printer in VFP or Windows do you still see it?

You may want to submit a bug report and attach an FRX with the printer environment saved. This will provide the most information possible about the conditions that would cause this. TIA.

>L<