BUG: SQL-DMO Call GetObjectByName May Cause GPF Under VBALast reviewed: May 1, 1997Article ID: Q137733 |
The information in this article applies to:
SYMPTOMSWhen 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. CAUSEIf a second parameter is explicitly passed to ::GetObjectByName rather than using its default value, the GP fault is encountered.
WORKAROUNDThe ::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); STATUSMicrosoft 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
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |