BUG: "MS Visual Basic- Printer Error" Occurs Under Windows 95

Last reviewed: March 11, 1997
Article ID: Q145729
3.00 WINDOWS 95 kbprg kbbuglist

The information in this article applies to:

  • Standard and Professional Editions of Microsoft Visual Basic for Windows, versions 3.0
  • Microsoft Windows 95

SYMPTOMS

The error message "Printer Not ready" is returned from Microsoft Windows 95 when attempting to print to a network printer with a space in the name of the server.

WORKAROUND

Rename the computer such that its name does not include an embedded space, or create a local printer that has the specified port redirected to the shared network printer. For more information on this please refer to the Microsoft Windows 95 documentation.

STATUS

Microsoft has confirmed this to be a problem in Visual Basic version 3.0 for Windows. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Steps to reproduce problem

  1. Rename a network computer, selecting a new name containing an embedded space.

  2. Create a shared networked printer on that computer.

  3. From a Microsoft Windows 95 computer connect to the network printer created in step #2 and make it the default printer.

  4. From Visual Basic, attempt to print anything, either in code or the IDE. The system error "MS Visual Basic - Printer Error" occurs.


KBCategory: kbprg kbbuglist
KBSubcategory:
Additional reference words: 3.00 buglist3.00

Keywords : kbbuglist kbprg
Version : 3.00
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 11, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.