Custom Form Printing

[Bryan Dickerson]

I'm converting a custom form from using lots of existing UserProperties
fields to now storing much of the information on a real database, but a user
showed me a print of a task (not a screen capture), and I remembered that
the prints from my new form are going to be radically affected as much of
the data will not be stored in the task anymore. Hmm... In designing the
custom form, do I have any control over the way it prints?

Thanx!

 

[Sue Mosher [MVP-Outlook]]

If you want to control what prints, write your own code, which can query the
database or use whatever the Outlook controls are showing. See
http://www.outlookcode.com/d/customprint.htm for ideas. The Word template
technique is the most flexible and highly recommended.

 

[Bryan Dickerson]

Ok, next question (to which I think I know the answers, but I want to see if
my thinking is correct): None of these methods or any other one that I could
write would affect the "File", "Print" menu option when I'm viewing/using my
custom form or the "Print" context menu option that's available when I'm
looking at a list of items in the folder, right?

 

[Sue Mosher [MVP-Outlook]]

Correct, although some people disable the File | Print command if they have
their own printing code.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Bryan Dickerson]

I think the one that I'm most 'afraid' of at this point is the context menu
option, because when the custom form is not open, some of the data is not
with the task and the print of it would confuse and dismay those who don't
understand. While it's open, all the fields are 'filled in' and it would
print fine. Ah, the dilemma....

 

[Sue Mosher [MVP-Outlook]]

I feel this is a matter of training and feedback. If the user learns that
printing with the item open gives them a good printout, that's the method
they'll use.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers