>Obviously, something's misbehaving when using the PROMPT clause in report command. I'm just wonder, however, if accessing SYS(1037), GETPRINTER() or even the the Common Dialogs ActiveX control's printer functionality would cause the same problem. This sort of behavior makes me very upset with the provider.
>
>< DukeDaddy metamorphosizes into "The Duke" >
>
>The Duke says this. The Duke says that he'd like to get the Senior Developer for the printer drivers from HP into a room along with one of those well engineered, well manufactured, HP Laser printers that's as big as a microwave oven. The Duke would then explain to that rooty-poo that those well engineered, well manufactured, HP Laser printers that are as big as a microwave oven aren't worth a pile of steaming monkey crap if they don't have drivers that conform to Microsoft's DDK specifications. If he protested saying that he didn't think it makes a difference, the Duke would tell him in no uncertain terms that, in the final analysis, It doesn't matter what he thinks. The only thing that matters is that the well engineered, well manufactured, HP Laser printers that are as big as a microwave oven work as they're supposed to. The Duke would then take that engineered, well manufactured, HP Laser printer that's as big as a microwave oven, turn it sideways, and stick it straight
>up his candy...As you can see, the Duke gets slightly aggitated about this subject.
>
>The Duke humbly apologizes to you for this rant.
>
>Hey, folks it's Friday. Remember "Fun Fridays"?

LOL! HP *definitely* needs to experience that!