BUG: Current Database Not Correct After Use in Query Window

 Last reviewed: April 30, 1997
Article ID: Q121022

The information in this article applies to: 

  - Microsoft SQL Server version 4.2b for OS/2
  - Microsoft SQL Server version 4.2
BUG# 10141 (4.2)

SYMPTOMS

Doing a use <databasename> in the query window will reset the database named in the current database list box. However, the prior database listed in the box is the one still active as the current database.

Issuing a use command in a query window in Object Manager may cause the database listed in the current database list box to be incorrect. For example, if an sa whose default database is master connects with Object Manager, then opens a query window and issues the commands, 

   use pubs
   go
   select * from authors
   go
and then closes the query window, the current database list box will indicate pubs is the current database. If the sa then clicks the objects button, the objects listed will be from the master database, not pubs.

WORKAROUND

Select the correct database in the current database list box to reset the current database, then reclick the objects window.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 4.2 and SQL Server version 4.2b for OS/2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: Windows NT
Keywords : kbbug4.20 kbtool SSrvObj_Man SSrvWinNT
Version : 4.2b | 4.2
Platform : OS/2 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 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.