Microsoft Knowledge Base Email Alertz

KBAlertz.com: (892608) - Describes a problem that may occur in Access 2003. You may receive the Syntax error in INSERT INTO statement error message. Jet 4.0 reserved words that are used in the column names of your database table may cause this problem to occur.

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]






Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

You may receive a "Syntax error in INSERT INTO statement" error message when you use ADO.NET code to access Office Access 2003

Article ID:892608
Last Review:March 9, 2006
Revision:1.2

SYMPTOMS

You may receive the following error message when you use Microsoft ADO.NET code to access Microsoft Office Access 2003:
Syntax error in INSERT INTO statement
This problem may occur when you run the Update function that is related to an Access 2003 database. Additionally, you use the OleDbDataAdapter class and the DataSet class.

Back to the top

CAUSE

This problem may occur if your database table contains column names that use Microsoft Jet 4.0 reserved words.

Back to the top

RESOLUTION

Change the column names in your database table so that you do not use Jet 4.0 reserved words.

For additional information about Jet 4.0 reserved words, click the following article number to view the article in the Microsoft Knowledge Base:
248738 (http://kbalertz.com/Feedback.aspx?kbNumber=248738/) List of reserved words in Jet 4.0

Back to the top

STATUS

This behavior is by design.

Back to the top


APPLIES TO
•Microsoft ADO.NET 2.0
•Microsoft ADO.NET 1.1
•Microsoft Office Access 2003

Back to the top

Keywords: 
kbtshoot kbprb KB892608

Back to the top

   

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Steve Takach Reported as Irrelevant  
Written: 5/17/2005 1:10 AM
This solved all my problems. The error message ado.net returns should be more informative (or access should not allow reserved words as column names) as i spent countless hours trying to work this one out.

MeToo Reported as Irrelevant  
Written: 8/2/2005 10:51 PM
I should have searched the internet ealier instead of wasting some hours this night on this issue :-( After changing column names everything works now :-)

Anonymous User Reported as Irrelevant  
Written: 2/15/2006 4:45 PM
Thank you so much! I have spent several hours with this problem and it's now fixed thanks to you. I guess that this may be one reason for using appropriate naming conventions for everything. I have learned my lesson.

satya - satya_akula NOSPAM-AT-NOSPAM reiffmail.com Reported as Irrelevant  
Written: 3/3/2006 4:37 AM
put that reserved word in square brackets([])in query expression then ado.net won't give u any error

Jenice - vampirakhell NOSPAM-AT-NOSPAM hotmail.com Report As Irrelevant  
Written: 11/28/2007 10:04 PM
hi, my english is poor but i can't leave of this page without try tell us: this page solve all my problems, thanks, i can continue with my homework now... every day we can learn something new.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please