PRB: CLongBinary Edits Fail with SQL Server Snapshot

Last reviewed: June 26, 1997
Article ID: Q156296

The information in this article applies to:

The Microsoft Foundation Classes (MFC) included with: - Microsoft Visual C++, 32-bit Edition, versions 4.0, 4.1, 4.2

SYMPTOMS

When calling CRecordset::Edit() followed by CRecordset::Update() to update an image field in a snapshot recordset, you may receive the following errors:

   Incorrect syntax near the keyword 'UPDATE'.
   State:37000,Native:156,Origin:[Microsoft][ODBC SQL Server Driver]
                                 [SQL Server]

   Line 1: Incorrect syntax near '='.
   State:37000,Native:170,Origin:[Microsoft][ODBC SQL Server Driver]
                                 [SQL Server]

CAUSE

There is a bug in the Microsoft SQL Server ODBC driver version 2.65.0201, which ships with Visual C++ version 4.2.

RESOLUTION

Upgrade your SQL Server ODBC driver to version 2.65.0213, which comes with Microsoft Visual C++, Enterprise Edition, version 4.2 or with the Service Pack 1 for Microsoft SQL Server version 6.5.

MORE INFORMATION

This problem occurs only when the cursor library is loaded and the recordset is opened as a snapshot. Dynasets without the cursor library do not display this problem.

REFERENCES

For additional information, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q152709
   TITLE     : FIX: Update of BLOB Data w/SQL Server 2.65.0201 Driver
                    Stops

Keywords : kberrmsg kbprg MfcDatabase kbprb kbprg
Technology : kbMfc
Version : 4.0 4.1 4.2
Platform : NT WINDOWS
Issue type : kbprb

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: June 26, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.