Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

BUG: "Syntax Error in INSERT INTO..." on ADO Recordset.Update

View products that this article applies to.

This article was previously published under Q189220

↑ Back to the top


When you call the AddNew method, and then call the Update method of a Recordset, the following error is returned:
Microsoft OLE DB Provider for ODBC Drivers error '80040e21'
[Microsoft][ODBC Microsoft Access 97 Driver] Syntax error in INSERT INTO statement.
Using the Microsoft Access ODBC Driver version4.00.4202.00 or later, the error message is:
Run-time error '-2147467259(80004005)':
[Microsoft][ODBC Microsoft Access Driver]Syntax error in INSERT INTO statement.

↑ Back to the top


This error occurs if the following are true:
  • The CursorType is adOpenForwardOnly (0).
  • The CursorLocation is adUseServer.
  • A field being updated has a space in the field name.
  • You are using the Microsoft Access ODBC driver.
Calling the AddNew and Update methods, on a Server-Side, Forward-Only cursor, is an invalid operation. ActiveX Data Objects (ADO) compensates for this code flaw by generating an INSERT statement to perform the operation. When ADO generates the INSERT statement, it does not delimit the field names. Therefore, field names that contain a space generate a syntax error.

For example, a valid INSERT statement would be as follows:
   INSERT INTO Table ([field with space]) Values(value)
ADO generates the following code:
   INSERT INTO Table (field with space) Values(value)

↑ Back to the top


Here are several possible resolutions:
  • Do not use spaces in the field names in your database.
  • Use a CursorLocation of adUseClient (3).
  • Do not use a CursorType of adOpenForwardOnly (0), such as adOpenKeyset (1), adOpenDynamic (2), or adOpenStatic (3).
  • Perform the operation by generating your own INSERT statement, with delimiters on the field names, instead of using the AddNew and Update methods.
  • Use the Microsoft OLE DB Provider for Jet version 3.51 or 4.0 instead of the Microsoft OLE DB Provider for ODBC and the Microsoft Access ODBC Driver.

↑ Back to the top


Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

↑ Back to the top

Keywords: kbbug, kbdatabase, kbdriver, kbjet, KB189220

↑ Back to the top

Article Info
Article ID : 189220
Revision : 4
Created on : 3/2/2005
Published on : 3/2/2005
Exists online : False
Views : 422