>Fox PowerPrinter does two things:
>
>1) It strips all the printer specific crap from the FRX.
>2) It provides a wrapper around the low level API printer calls. Anything exposed by the printer driver can be controlled.

oh... so ok, it would of worked for me then. Thing is this is a rush job and I've already dealt with enough dll hell that I just dont want to pull in one more dll at this point. I'll make note though of this info you gave me for next release, thanks!

And for the record, doing the Crystal oReport.PrinterSetup(0) did allow me to still keep my spec's promise of providing printer setup manipulation. So it fixed my problem without resorting to another dll. But one caveat... Crystal's PrinterSetup() method does an implicit PrintOut() when you click OK button. So downside was I lost a separated print setup step, but we can live with that. I thought this was kinda dumb though, especially since I can do PrintOut(1) and get prompted for number of copies and print range, seems to me that shouldnt of been coupled but oh well.

Thanks again for the input.