BUG: SQL-DMO Call GetObjectByName May Cause GPF Under VBA

Last reviewed: May 1, 1997
Article ID: Q137733

The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG# NT: 11276 (6.00)

SYMPTOMS

When you use the SQL-DMO function ::GetObjectByName in the Visual Basic for Applications environment, you may encounter a general protection (GP) fault.

A GP fault could occur when a call to the ::GetObjectByName function is invoked, resulting in the message:

   The instruction at "0x1d0fc7cd" referenced memory at "0x73737373"
   The memory could not be read.

CAUSE

If a second parameter is explicitly passed to ::GetObjectByName rather than using its default value, the GP fault is encountered.

WORKAROUND

The ::GetObjectByName does not exhibit the same behavior when used in the C/C++ environment. Both the default and a specific object type can be provided, as shown below:

   LPSQLOLEDBOBJECT pSQLObject;

      pSQLDatabase->GetObjectByName("authors", &pSQLObject);

     pSQLDatabase->GetObjectByName("authors",
               &pSQLObject, SQLOLEObj_UserTable);

STATUS

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


Additional query words: sql6
Keywords : kbbug6.00 kbprg SSrvDMO SSrvPrg
Version : 6.0
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: May 1, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.