Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/172105

From BetaArchive Wiki

Article ID: 172105

Article Last Modified on 12/10/2003


  • Microsoft Visual Basic 5.0 Control Creation Edition
  • Microsoft Visual Basic 5.0 Learning Edition
  • Microsoft Visual Basic 5.0 Professional Edition
  • Microsoft Visual Basic 5.0 Enterprise Edition

This article was previously published under Q172105


If a call is made to the EndDoc method of the Printer Object (or the application is closed) after having issued the NewPage method, a page is ejected from the printer regardless of whether any actual printing has taken place.

This is contrary to the behavior of Visual Basic 4.0, as well as the online Help in Visual Basic 5.0 for the EndDoc method, which states the following:

If EndDoc is invoked immediately after the NewPage method, no additional blank page is printed.


To work-around this problem, do not call the NewPage method until you know you are going to print something on the page.


Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been fixed in Visual Basic 6.0.


Steps to Reproduce Behavior

  1. Create a new project.
  2. Add a CommandButton to Form1.
  3. Add the following code to Form1:

          Private Sub Command1_Click()
             Printer.Print "Page 1"
          End Sub
  4. Press the F5 key to run the project.
  5. Click the button. Note that two pages are printed. The first page prints as expected, but it is followed by a blank page.


Visual Basic 5.0 Online Help for the EndDoc Method

Additional query words: kbVBp500bug kbVBp600fix kbVBp kbdsd kbDSupport kbControl

Keywords: kbbug kbfix KB172105