blocks|key|542462|text|当表名或列名包含一个空格或它是一个保留字时，您需要将该名称括在方括号中，以避免混淆为解释命令而调用的sql解析器。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|542463|在你的上下文中，你应该写|542464|command.CommandText+=+"INSERT+INTO+[statement+workers]+values(?,?,?,?,?,?,?,?,?)";|code-block|syntax|javascript|542465|编辑|style|BOLD|542466|在查看了您的字段的名称(并假设字段的顺序与您键入的字段完全相同)之后，您应该更改添加参数的顺序，以与表中字段的顺序完全匹配。|542467|OleDb不能使用命名占位符来设置参数集合，因此必须严格遵循字段顺序。|542468|如果不这样做，那么一个值最终可能会出现在另一个字段中，从而产生问题，比如当您试图在date字段中存储一个十进制值时。(当然，如果在表名之后添加列名，则可以更改顺序)|542469|command.Connection+=+connection;
command.CommandText+=+"INSERT+INTO+statement+workers+values(?,?,?,?,?,?,?,?,?)";
command.Parameters.Add("@Tab",+OleDbType.Integer).Value+=+Convert.ToInt32(+tabtextBox1.Text);
command.Parameters.Add("@User",+OleDbType.VarWChar).Value+=+usertextBox2.Text;
command.Parameters.Add("@Pass",+OleDbType.VarWChar).Value+=+passtextBox4.Text;
command.Parameters.Add("@Names",+OleDbType.VarWChar).Value+=+namestextBox3.Text;
command.Parameters.Add("@Tele",+OleDbType.Integer).Value+=+Convert.ToInt32(teletextBox6.Text);
command.Parameters.Add("@Job",+OleDbType.VarWChar).Value+=+jobtextBox9.Text;
command.Parameters.Add("@Date",+OleDbType.Date).Value+=+dateofdateTimePicker2.Value;
command.Parameters.Add("@DOB",+OleDbType.Date).Value+=+dateTimePicker1.Value);
command.Parameters.Add("@Pay",+OleDbType.Decimal).Value+=+Convert.ToDecimal(paytextBox7.Text);
command.ExecuteNonQuery();|542470|通过这种方式，您可以按照表字段所期望的确切顺序设置值。|542471|注意，我已经用更精确的AddWithValue删除了危险的Add，后面跟着字段所期望的数据类型。|CODE|542472|AddWithValue无法知道数据库所期望的类型，因此可以查看参数的类型。因为您传递所有字符串，所以数据库引擎被迫将它们转换回预期的字段类型。|542473|有时(特别是对于日期和十进制字段)，这是不正确的。|542474|边注：|542475|电话号码不应该存储为号码，它们不是。|ordered-list-item|542476|从安全的角度来看，密码永远不应该存储在clear+text.There中，许多文章解释了这是如何危险的，以及如何散列密码。您可以从这里开始搜索：在数据库中存储密码的最佳方法|542477|entityMap|0|LINK|mutability|MUTABLE|url|https://support.office.com/en-us/article/Access-2007-reserved-words-and-symbols-e33eb3a9-8baa-4335-9f57-da237c63eabe?CorrelationId=f03e97a5-01d2-4ed7-aa40-48d2da9d5215&ui=en-US&rs=en-US&ad=US|1|https://stackoverflow.com/questions/1054022/best-way-to-store-password-in-database^0|H|3|0|0|0|0|0|2|0|0|0|0|0|0|B|C|T|3|0|0|0|0|0|20|E|1|0^^$0|@$1|2|3|4|5|6|7|1M|8|@]|9|@$A|1N|B|1O|1|1P]]|C|$]]|$1|D|3|E|5|6|7|1Q|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|1R|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|1S|8|@$A|1T|B|1U|M|N]]|9|@]|C|$]]|$1|O|3|P|5|6|7|1V|8|@]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1W|8|@]|9|@]|C|$]]|$1|S|3|T|5|6|7|1X|8|@]|9|@]|C|$]]|$1|U|3|V|5|H|7|1Y|8|@]|9|@]|C|$I|J]]|$1|W|3|X|5|6|7|1Z|8|@]|9|@]|C|$]]|$1|Y|3|Z|5|6|7|20|8|@$A|21|B|22|M|10]|$A|23|B|24|M|10]]|9|@]|C|$]]|$1|11|3|12|5|6|7|25|8|@]|9|@]|C|$]]|$1|13|3|14|5|6|7|26|8|@]|9|@]|C|$]]|$1|15|3|16|5|6|7|27|8|@]|9|@]|C|$]]|$1|17|3|18|5|19|7|28|8|@]|9|@]|C|$]]|$1|1A|3|1B|5|19|7|29|8|@]|9|@$A|2A|B|2B|1|2C]]|C|$]]|$1|1C|3|-4|5|6|7|2D|8|@]|9|@]|C|$]]]|1D|$1E|$5|1F|1G|1H|C|$1I|1J]]|1K|$5|1F|1G|1H|C|$1I|1L]]]]

When a table name or column name contains a space or it is a <a href="https://support.office.com/en-us/article/Access-2007-reserved-words-and-symbols-e33eb3a9-8baa-4335-9f57-da237c63eabe?CorrelationId=f03e97a5-01d2-4ed7-aa40-48d2da9d5215&amp;ui=en-US&amp;rs=en-US&amp;ad=US" rel="nofollow noreferrer">reserved word</a> you need to enclose that name in square brackets to avoid confusing the sql parser called to interpret your command. 
In your context you should write

<pre><code>command.CommandText = "INSERT INTO [statement workers] values(?,?,?,?,?,?,?,?,?)";
</code></pre>

EDIT 
After looking at your field's name (and assuming that the order of fields is exactly as you have typed them) then you should change the order in which you add your parameters to match exactly the order of the fields in your table. 
OleDb cannot use named placeholders to setup the parameter collection and thus, it is important to strictly follow the field order. 
If you don't do it then a value could end up in a different field and create problems like when you try to store a decimal value in a date field. (Of course if you add the column names after the table name the order could be changed)

<pre><code>command.Connection = connection;
command.CommandText = "INSERT INTO statement workers values(?,?,?,?,?,?,?,?,?)";
command.Parameters.Add("@Tab", OleDbType.Integer).Value = Convert.ToInt32( tabtextBox1.Text);
command.Parameters.Add("@User", OleDbType.VarWChar).Value = usertextBox2.Text;
command.Parameters.Add("@Pass", OleDbType.VarWChar).Value = passtextBox4.Text;
command.Parameters.Add("@Names", OleDbType.VarWChar).Value = namestextBox3.Text;
command.Parameters.Add("@Tele", OleDbType.Integer).Value = Convert.ToInt32(teletextBox6.Text);
command.Parameters.Add("@Job", OleDbType.VarWChar).Value = jobtextBox9.Text;
command.Parameters.Add("@Date", OleDbType.Date).Value = dateofdateTimePicker2.Value;
command.Parameters.Add("@DOB", OleDbType.Date).Value = dateTimePicker1.Value);
command.Parameters.Add("@Pay", OleDbType.Decimal).Value = Convert.ToDecimal(paytextBox7.Text);
command.ExecuteNonQuery();
</code></pre>

In this way you set the values in the exact order expected by the table fields. 
Notice that I have removed the dangerous <code>AddWithValue</code> with a more precise <code>Add</code> followed by the datatype expected by the field. 
AddWithValue cannot know what is the type expected by the database and thus looks at the type of the parameter. Since you pass all strings then the database engine is forced to convert them back to the expected field type. 
Sometime (in particular with dates and decimal fields) this doesn't work correctly. 

Side notes: 

<ol>
<li>Telephone numbers should not be stored as numbers, they are not.</li>
<li>From a security point of view, a password should never be stored in
clear text.There are many articles that explain how this is dangerous and how to hash a password. You could start your search from here: <a href="https://stackoverflow.com/questions/1054022/best-way-to-store-password-in-database">Best way to store password in database</a></li>
</ol>

blocks|key|272228|text|另外，您必须使用DateTimePickers的值，而不是字符串：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|272229|command.Parameters.AddWithValue("@Date",+dateofdateTimePicker2.Value);
command.Parameters.AddWithValue("@DOB",+dobdateTimePicker1.Value);|code-block|syntax|javascript|272230|并说明字段名：|272231|command.CommandText+=+"INSERT+INTO+[statement+workers]+(fielname1,+fieldname2,+..,+fieldname9)+values(?,?,?,?,?,?,?,?,?)";|272232|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Also, you must use the values of the DateTimePickers, not strings:

<pre><code>command.Parameters.AddWithValue("@Date", dateofdateTimePicker2.Value);
command.Parameters.AddWithValue("@DOB", dobdateTimePicker1.Value);
</code></pre>

and to state the field names:

<pre><code>command.CommandText = "INSERT INTO [statement workers] (fielname1, fieldname2, .., fieldname9) values(?,?,?,?,?,?,?,?,?)";
</code></pre>

I can't seem to get were I am making the mistake. 

<pre><code> OleDbCommand command = new OleDbCommand();

 command.Connection = connection;
 command.CommandText = "INSERT INTO statement workers values(?,?,?,?,?,?,?,?,?)";
 command.Parameters.AddWithValue("@Tab", tabtextBox1.Text);
 command.Parameters.AddWithValue("@User", usertextBox2.Text);
 command.Parameters.AddWithValue("@Pass", passtextBox4.Text);
 command.Parameters.AddWithValue("@Names", namestextBox3.Text);
 command.Parameters.AddWithValue("@Tele", teletextBox6.Text);
 command.Parameters.AddWithValue("@Job", jobtextBox9.Text);
 command.Parameters.AddWithValue("@Pay", paytextBox7.Text);
 command.Parameters.AddWithValue("@Date", dateofdateTimePicker2.Value.ToShortDateString());
 command.Parameters.AddWithValue("@DOB", dobdateTimePicker1.Value.ToShortDateString());
 command.ExecuteNonQuery();


 MessageBox.Show("Data Saved");
</code></pre>

after I try to insert details it giving me the response:

<blockquote>
 oledbexception was unhandled syntax error in insert into statement
</blockquote>

oledbexception was unhandled syntax error in insert into statement

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

如果我犯了这个错误，我似乎无法理解。        OleDbCommand command = new OleDbCommand();        command.Connection = connection;        command.CommandText = "INSERT INTO statement...

问oledbexception在insert into语句中出现未处理语法错误
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问oledbexception在insert into语句中出现未处理语法错误EN