Prev: Inserting multiple pictures into a Word table cell
Next: Using a Space in Webbrowser Control
From: Mojo on 28 Mar 2010 13:44
Hi Mike/Dave

Sorry for the late reply. I didn't mean to be disrespectful, especially in
light of the brilliant assistance you have given me on this.

I just haven't been on my machine to check your responses until today.

Thank you once again.

"Mike Williams" <Mike(a)WhiskyAndCoke.com> wrote in message
news:%23YQy8EktKHA.3904(a)TK2MSFTNGP02.phx.gbl...
"Mojo" <please(a)dont.spam.com> wrote in message
news:um3vclitKHA.4220(a)TK2MSFTNGP05.phx.gbl...

> Any good tips without the need to use/register an ocx?

One thing I forgot to mention in my previous response is that you should
always use error trapping with your printing code, even if you are not doing
anything that appears likely to cause an error. In fact I really should have
done so in the code I just posted. It is even possible to get a error on the
very first Printer.Print statement under certain circumstances, even if the
user does actually have printers installed. So there's one tip . . . error
trapping ;-)

Mike



 | 
Pages: 1
Prev: Inserting multiple pictures into a Word table cell
Next: Using a Space in Webbrowser Control