I have been having some sporadic problems with my reports. They sometimes come crashing down and slam the GDI dll for graphics display. It seems to have something to do with what printer driver I have assigned when I edit and build a particular report, and that it conflicts with the driver used in the field. The reason the GDI is getting tromped on has something to do with the NO CONSOLE command, because if we take that off it works fine. Also, once it prints properly it will never crash. For example if we prompt the first time then it does not crash after that whether we use NO CONSOLE or not. I am curious as to why the reports need a particular driver to attach to at all. I can see that a label might need that, but for a report it should be able to just grab the default printer driver and print the report. Here are the specifics of my case. Using an HP 6 LP we utilize the driver HP Laser IIIP in the field. We do this because of some of the quirks associated with the 6P driver, and found this one to be more reliable. In the office, my associate uses an HP Laser Jet 5P. The problem started to arise when she started compiling under this driver.

Questions:
Has anyone else experienced this type of behavior?

Why must a driver be attached to the report at all? If the print is just textual, who cares? Or is there a way to assign, "Use Default" or something like that?

What if the end user decides that HP is not the printer thay want to use? Then I am in trouble and have to customize the report per installation?

Or .. am I just nuts here?

Stay Tuned to these reports in "As the Printer Turns" ...