BUG: Print to File Fails to Request Output File Name

• 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.

Back to the top

Steps to Reproduce Behavior

1. Start a new Visual Basic Standard EXE project. Form1 is created by default.
2. On the Project menu, select Components. In the Components dialog box, check the Microsoft Common Dialog Control component, and then click OK.
3. Add a CommonDialog control to Form1.
4. Add the following code to the General Declarations section of Form1:

   Private Sub Form_Click()
       Dim blnUseWorkaround As Boolean
   
       ' Uncomment the following line to examine a workaround
       'blnUseWorkaround = True
   
       CommonDialog1.ShowPrinter
       
       If blnUseWorkaround Then
           ' Test to see if the Print to File box is checked
           If (CommonDialog1.Flags And cdlPDPrintToFile) = cdlPDPrintToFile Then
               MsgBox "Create the Output file using the Open, Write, and Close commands"
           Else
               PrintText
           End If
       Else
           PrintText
       End If
   End Sub
   
   Sub PrintText()
       Printer.Print "Test Text"
       Printer.EndDoc
   End Sub
   					

5. Press the F5 key to run the program.
6. Click on Form1, and note that the Print dialog box appears.
7. Check the Print to File checkbox.
8. Click OK on the Print dialog box, and note that the dialog box that requests an Output File Name is not displayed.

Back to the top