BUG: W3DBVER Generates Errors in Debug Windows 3.1

 Last reviewed: April 28, 1997
Article ID: Q99678

The information in this article applies to:
  • Microsoft SQL Server Programmer's Toolkit, version 4.2
BUG# 8617 (4.2.32)

SYMPTOMS

Starting then exiting the W3DBVER utility dated 3/22/93 in debug Windows 3.1 generates the following errors and warnings: 

   err W3DBVER SHOWWINDOW+C: Invalid HWND: 0x0000
   err W3DBVER SHOWWINDOW+C: Invalid HWND: 0x0000
   err W3DBVER->W3DBLIB GLOBALHANDLE+C: Invalid HANDLE: 0x0000
   wn W3DBVER USER: DestroyWindow: Unremoved window property
   wn W3DBVER USER: DestroyWindow: Unremoved window property
   err W3DBVER SHOWWINDOW+C: Invalid HWND: 0x295c
   err W3DBVER SHOWWINDOW+C: Invalid HWND: 0x29b4
   wn W3DBVER GDI: Font not deleted: 0D6A
Each of the "err" lines is also followed by: 

   FatalExit code = 0xNNNN
   Abort, Break, Exit or Ignore?

WORKAROUND

Start the DBWIN application that comes with debug Windows 3.1, choose the Settings command from the Options menu, and check the "Don't Break on Errors" options. This will avoid the FatalExit prompt.

STATUS

Microsoft has confirmed this to be a problem in DB-Library version 4.20.32. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: W3DBVER FatalExit debug
Keywords : kbinterop SSrvProg SSrvVisB
Version : 4.2.32
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: April 28, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.