BUG: Print to File Fails to Request Output File Name (274523)
The information in this article applies to:
- Microsoft Visual Basic Professional Edition for Windows 4.0, when used with:
- the operating system: Microsoft Windows 95
- the operating system: Microsoft Windows 98
- Microsoft Windows Millennium Edition
- Microsoft Visual Basic Professional Edition for Windows 5.0, when used with:
- the operating system: Microsoft Windows 95
- the operating system: Microsoft Windows 98
- Microsoft Windows Millennium Edition
- Microsoft Visual Basic Professional Edition for Windows 6.0, when used with:
- the operating system: Microsoft Windows 95
- the operating system: Microsoft Windows 98
- Microsoft Windows Millennium Edition
- Microsoft Visual Basic Enterprise Edition for Windows 4.0, when used with:
- the operating system: Microsoft Windows 95
- the operating system: Microsoft Windows 98
- Microsoft Windows Millennium Edition
- Microsoft Visual Basic Enterprise Edition for Windows 5.0, when used with:
- the operating system: Microsoft Windows 95
- the operating system: Microsoft Windows 98
- Microsoft Windows Millennium Edition
- Microsoft Visual Basic Enterprise Edition for Windows 6.0, when used with:
- the operating system: Microsoft Windows 95
- the operating system: Microsoft Windows 98
- Microsoft Windows Millennium Edition
This article was previously published under Q274523 SYMPTOMS
When the Print to File checkbox is selected in the Print dialog box, the dialog box that allows an Output File Name to be specified is not displayed.
RESOLUTION
There are three possible workarounds for this behavior:
- Check the Flags property of the CommonDialog control to see if the Print to File checkbox is marked. If the checkbox is marked, you can create a text file (without printer codes) with the Visual Basic Open, Write, and Close commands.
- Configure a local printer to print to the FILE: port. This local printer can be used when a Print to File operation is required.
- Open the Printer Common Dialog with WIN32 API functions, such as PrintDlg or PageSetupDlg, instead of with the comdlg32.ocx file. You can then print with API calls instead of the Printer object. See the "References" section of this article for more information.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. REFERENCESFor additional information about using the WIN32 API functions for common dialog boxes and printing, click the article numbers below
to view the articles in the Microsoft Knowledge Base:
175535 PRB: Printing Rotated Text with Visual Basic
180645 FIX: Cannot Change Page Settings During Print Job
173981 PRB: Behavior Differences of Print Dialog Box on Different Platforms
Modification Type: | Minor | Last Reviewed: | 9/28/2004 |
---|
Keywords: | kbBug kbCmnDlgPrint kbCtrl kbFileIO kbpending KB274523 |
---|
|