Microsoft KB Archive/90864

= ACC: Microsoft Access Saves Printer Information with Each Form or Report =

Article ID: 90864

Article Last Modified on 1/18/2007

-

APPLIES TO


 * Microsoft Access 1.0 Standard Edition
 * Microsoft Access 1.1 Standard Edition
 * Microsoft Access 2.0 Standard Edition
 * Microsoft Access 95 Standard Edition
 * Microsoft Access 97 Standard Edition

-



This article was previously published under Q90864



Novice: Requires knowledge of the user interface on single-user computers.



SUMMARY
Microsoft Access saves printer driver information with each form or report that it generates. This means you do not have to set up the printer with the correct driver in order to print out a form or report--the form or report &quot;remembers&quot; the correct driver and uses it. For example, you can save one form using a PostScript printer driver and another form using the generic text driver.

NOTE: If the Default Printer option button is selected, the form will be printed to the Windows default printer.



MORE INFORMATION
If the printer that the printer driver requires is not currently connected, Microsoft Access displays a dialog box stating that the printer is not available and enables you to select another printer.

Bear in mind that some text formatting depends on the current printer driver. For example, if you format a document with a PostScript printer font instead of a software font (such as a TrueType font) and send the document to a PostScript printer, everything should be printed correctly. However, if you send the document to a LaserJet, you will receive output errors because some PostScript printer fonts are not available on a LaserJet.

A driver-related problem could be something such as the sudden appearance of the Zapf Dingbats font in a form or report set up to use the Windows System font and sent to a PostScript printer. This problem occurs because the Windows System font is not available on PostScript printers. When a font is unavailable, Windows attempts to find an equivalent among those on the printer, searching through them alphabetically. In this case, it arrives at the Zapf Dingbats font last and uses it because there are no other options.

The best way to avoid these problems is to create all your forms and reports with TrueType fonts, which appear correctly in print preview and are processed the same way by all printers.

Additional query words: printing post script true type

Keywords: kbinfo kbusage KB90864

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.