Discussion Locked

ACCESS 2000 PRTDEVMODE,PRTDEVNAMES

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Need alot of help in this, could use custom form under Windows 2000, but now that we have gone to Windows 2000 Pro lost that option so have to now setup all printing options in VB, could use some sample code for how to setup custom form size or selecting a certain bin. Thanks

5 replies

by maxwell edison

Method 1: Changing the Default Printer.

In the Page Setup (or Print Setup in version 2.0) dialog box, you can choose whether forms or reports are printed by either a default printer or a specific printer. If you choose a default printer, the formor report is printed to the Microsoft Windows default printer. If you want to change to another default printer, you must change the Microsoft Windows default printer.

To change the default printer using Visual Basic code (or Access Basic code in version 2.0 or earlier), use WriteProfileString to change the Device= entry of the Microsoft Windows section of the Win.ini file.

Method 2: Setting the PrtDevNames and PrtDevMode properties.

The PrtDevNames property stores the name of the printer, and the PrtDevMode property stores the driver information. Both of these properties need to be changed in order to change the printer driver. If the PrtDevMode property does not match the PrtDevNames property (that is, the PrtDevMode property describes a different driver than the PrtDevNames property) a General Protection (GP) Fault may occur.

To change the printer driver, you must do the following:

Open a form or report in Design view.

Set the PrtDevNames property.

Retrieve and set the PrtDevMode property.

In order to set the PrtDevMode property to the appropriate structure, the driver information must be obtained. There are several ways to obtain this information:

Retrieve the information from a previously saved form or report that uses the desired printer.

Call the driver and retrieve the structure. In order to call the driver, a separate DLL is needed. This is because calls to functions in outside files must be declared ahead of time and the driver name will not be known. Instead, call a DLL that determines the correct printer driver to call and retrieves the DevMode structure.

Use the Windows Print Common Dialog.

This discussion is closed to new replies.