>Do you force ActiveX method to print itself (meaning clear printout)
>or does it end up as some high resolution bitmap at the end, and then gets printed as such ?

Not every ActiveX supports the ability to print itself, like the Rich Text control, however, every ActiveX control does have the ability to render itself to a device context, including a printer's HDC, using the iViewObject.Draw method.

For printing purposes, I prefer to to render to the HDC of an EMF and then send the EMF to the print job. This gives you more control over how the object will be rendered and I don't get as many wierd stretching problems that can occur with EMFs and certain video drivers.

I also prefer EMFs over bitmaps for printing, because the EMF format is native to the Windows print engine and will render the highest quality for the printer device. If you choose to use BITMAPs, you always have to wonder what the best resolution might be for printing...300dpi? 1200dpi?...the bigger you go, the longer it could take to render and if you use PDF print drivers, the larger the output PDF will become. If you use EMFs, you get better quality, performance and size.

Of course there are always exceptions to the rule. Some ActiveX controls will only look good when rendered as BITMAPs and only at screen resolution. But this is rare for the ActiveX controls I need to print.

>BTW see PM.
Sorry I missed something, which PM are you refering?