Duplex by Default

One of the niftiest features on many top-end printers is that they can duplex your documents. This means that they will print on both sides of a piece of paper. While the printing time is not decreased, the paper consumed by a print job is cut in half.

Assuming you have the latest printer driver for your printer, you can use the Properties dialog box for the printer to specify that you want to print your document duplexed. You can get to these settings by selecting Print from the File menu and then clicking on Properties. Unfortunately, Word will not remember this setting from one Word session to the next, nor will it store the setting with the document (as some other programs allow).

The problem is further compounded by the fact that you cannot access the individual settings in the Properties dialog box for a printer through the use of VBA. The reason is that the settings are maintained by the printer driver, not by Word—and Word doesn't make the printer driver objects available in VBA.

Even so, it is theoretically possible to write a macro that will auto change a printer's Property settings, but it is definitely not a recommended option. Why? Because to change the printer's settings requires working with the Windows API. This is not an easy task by any stretch of the imagination. Thus, unless you want to become an expert VB/Win32 API programmer, you are stuck with having to set the duplex setting each time the document is opened and printed.

There is one exception to this, however. If your printer uses PCL (printer control language, used with many HP printers), you can set up a PRINT field in the header or footer of your document. The field contains a command that can be sent directly to the printer to turn on duplexing. Exactly how you create a PRINT field has been covered in other issues of WordTips. The field syntax to use is as follows:

{ PRINT 27"&l1S" }

Remember that his approach works only with printers that use the PCL printer driver (and the printer must support duplexing, of course). The approach will not work with PostScript printers, since PostScript doesn't control the printer, just what goes on the page. If you would like more information on the subject, refer to the following Knowledge Base article 135569.

http://support.microsoft.com/?kbid=135569