blocks|key|526656|text|我也有同样的问题。当我检查"Hoew+to+alter+the+data+definition+of+a+linked+table"时，我突然想到可以尝试将字段数据类型更改为NUMBER，看看该代码是否可以工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|526657|因此，我将代码更改为：|526658|ALTER+TABLE+XXXXX+ALTER+COLUMN+ID+NUMBER|code-block|syntax|javascript|526659|运行代码，没有任何问题！已检查表设计，字段数据类型已从Autonumber更改为Number。|526660|因此，我决定再次尝试原始代码：|526661|ALTER+TABLE+XXXX+ALTER+COLUMN+ID+COUNTER+(1,1)|526662|还有..。成功了！O.O|526663|我不明白为什么..。但它成功了..。|526664|尝试通过代码将数据类型更改为NUMBER，运行它，然后将其更改回COUNTER(1,1)，并查看是否像我的那样修复了错误……|526665|entityMap|0|LINK|mutability|MUTABLE|url|http://www.experts-exchange.com/Database/MS_Access/Q_21099860.html^0|2F|6|D|1H|0|0|0|0|0|0|0|9|3|0|0|E|6|W|C|0^^$0|@$1|2|3|4|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|F|3|G|5|6|7|1C|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|1D|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1E|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|1F|8|@]|D|@]|E|$]]|$1|Q|3|R|5|J|7|1G|8|@]|D|@]|E|$K|L]]|$1|S|3|T|5|6|7|1H|8|@$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|U|3|V|5|6|7|1K|8|@]|D|@]|E|$]]|$1|W|3|X|5|6|7|1L|8|@$9|1M|A|1N|B|C]|$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|Y|3|-4|5|6|7|1Q|8|@]|D|@]|E|$]]]|Z|$10|$5|11|12|13|E|$14|15]]]]

I was having the same problem. I was checking <a href="http://www.experts-exchange.com/Database/MS_Access/Q_21099860.html" rel="noreferrer">"Hoew to alter the data definition of a linked table"</a> when it occurred to me that I could try changing the field datatype to <code>NUMBER</code> and see if that code worked. 

So I changed the code to:

<pre><code>ALTER TABLE XXXXX ALTER COLUMN ID NUMBER
</code></pre>

Run the code with no problems! Checked the table design, and the field datatype had changed from Autonumber to Number.

So, I decided to try the original code again: 

<pre><code>ALTER TABLE XXXX ALTER COLUMN ID COUNTER (1,1)
</code></pre>

and... IT WORKED!!! <code>O.O</code>

I don't understand why... but it worked...

Try changing the datatype to <code>NUMBER</code> via code, run it, then change it back to <code>COUNTER(1,1)</code>, and see if you got the error fixed, like mine did...

blocks|key|5762163|text|我也有同样的问题，它已经解决了“压缩和修复”的MS+Access数据库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5762164|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I was having the same problem, and it has been solved by "Compact &amp; Repair" the MS Access database.

blocks|key|534947|text|回复晚了，但其他人可能也会发现这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|534948|通过更改|534949|DoCmd.RunSQL+"DELETE+*+FROM+YourTable"
CurrentDb.Execute+"ALTER+TABLE+YourTable+ALTER+COLUMN+ID+COUNTER(1,1)"|code-block|syntax|javascript|534950|至|534951|DoCmd.RunSQL+"DELETE+*+FROM+YourTable"
CurrentDb.Execute+"ALTER+TABLE+YourTable+ALTER+COLUMN+ID+COUNTER(1,2)"|534952|我的没有再给出一个错误，它确实“重置”了自动编号。|534953|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Late reply, but others may find this problem too.

By changing 

<pre><code>DoCmd.RunSQL "DELETE * FROM YourTable"
CurrentDb.Execute "ALTER TABLE YourTable ALTER COLUMN ID COUNTER(1,1)"
</code></pre>

to

<pre><code>DoCmd.RunSQL "DELETE * FROM YourTable"
CurrentDb.Execute "ALTER TABLE YourTable ALTER COLUMN ID COUNTER(1,2)"
</code></pre>

Mine did not give an error anymore, and it did "reset" the auto number.

blocks|key|3647836|text|ALTER+COLUMN+ID+NUMBER对我也有效，但它可能只有在空表的情况下才能使用，否则将ID字段设置回Autonumber+(ALTER+COLUMN+ID+COUNTER(此处的next+ID+number，1))将不起作用。至少不能手动设置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3647837|这是.mdb+Access+10+(2002)文件，放在Windows+XP下的任何用户目录之上的C://目录/中，由运行时2010打开。当它在用户目录中时，我从来没有注意到这样的行为，比如我的文档或桌面，但也许这是巧合，它会在某个时候发生。在使用该文件和该代码几年后，第一次发生了这种情况。|3647838|第二天编辑：|3647839|这似乎得到了部分解释。原因是排序顺序。该数据库是在以前使用此设置创建和使用的：|offset|length|style|BOLD|3647840|工具>选项>常规>新建数据库排序顺序>波兰语|3647841|但是在中间时间，程序中的这个设置被设置为>+General|3647842|现在它显示了这个错误。它可以很容易地修复设置返回>波兰语|3647843|并运行压缩和修复数据库(ALTER+COLUMN+ID+COUNTER再次开始工作)。到目前为止，我已经重复了几次，每次都有效。但是使用General+Compact+and+repair数据库是没有用的。|3647844|此子例程：|3647845|Private+Sub+IDProperties()

Dim+db+As+DAO.Database
Dim+tdf+As+DAO.TableDef
Dim+TableName+As+String
Dim+i+As+Integer
Dim+str+As+String

TableName+=+"the+name+of+table"

Set+db+=+CurrentDb()
Set+tdf+=+db.TableDefs(TableName)

For+i+=+0+To+tdf.Fields("ID").Properties.Count+-+1
++++On+Error+Resume+Next
++++str+=+str+&+vbNewLine+&+tdf.Fields("ID").Properties(i).name
++++If+Err+>+0+Then
++++++++str+=+str+&+vbNewLine+&+Err.Number+&+"+"+&+Err.Description
++++++++Err.Clear
++++End+If
++++str+=+str+&+"+=+"+&+tdf.Fields("ID").Properties(i).Value
++++If+Err+>+0+Then+str+=+str+&+";+"+&+Err.Number+&+"+"+&+Err.Description
++++On+Error+GoTo+0
Next
Set+tdf+=+Nothing

db.Close
Set+db+=+Nothing

Debug.Print+str

End+Sub|code-block|syntax|javascript|3647846|返回ID字段的排序顺序。对于返回sort+order+=+General的3259错误的表，ID+CollatingOrder+=+1045。因此，Access似乎在导入过程中更改了ID字段的排序顺序。这将是解决这个问题的第二种方法。或者将整个数据库导入到新的文件中。第三种方法是复制这样的表--它显然也改变了ID的CollatingOrder。最好是通过VBA更改排序顺序，但它是只读属性。|3647847|Private+Sub+GetCollatingOrder()

Dim+db+As+DAO.Database
Dim+tdf+As+DAO.TableDef
Dim+TableName+As+String

Set+db+=+CurrentDb()
Set+tdf+=+db.TableDefs("table+name")

MsgBox+"Collating+order"+&+_
+++vbNewLine+&+"-+database:+"+&+db.CollatingOrder+&+_
+++vbNewLine+&+"-+table:+"+&+tdf.Fields("ID").Properties("CollatingOrder").Value
+++'or+tdf.Fields("ID").CollatingOrder

Set+tdf+=+Nothing
db.Close
Set+db+=+Nothing

End+Sub|3647848|只能更改数据库排序顺序：|3647849|Application.SetOption+"New+Database+Sort+Order",+1033+'+or+1045+for+example|3647850|但它会改变某人数据库的属性。也许仍然需要紧凑和维修。|3647851|稍后编辑：|3647852|现在MsgBox显示1045+:+General和Polish+(以及:+db和ID)，并停止显示错误...非常奇怪。也许是因为几次紧凑和维修。|3647853|3647854|第二天，同样的错误，如果新的数据库排序顺序没有改变%2B压缩和修复。所以General在重启后停止了工作。在压缩和修复之前，ID和整个数据库的MsgBox中的CollatingOrder属性值是不同的，在压缩和修复之后也是如此(在压缩和修复之前更改了新数据库的排序顺序)。|3647855|entityMap^0|0|0|0|E|4|0|0|I|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1M|8|@$H|1N|I|1O|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1P|8|@$H|1Q|I|1R|J|K]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1S|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1T|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1U|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1V|8|@]|9|@]|A|$]]|$1|V|3|W|5|X|7|1W|8|@]|9|@]|A|$Y|Z]]|$1|10|3|11|5|6|7|1X|8|@]|9|@]|A|$]]|$1|12|3|13|5|X|7|1Y|8|@]|9|@]|A|$Y|Z]]|$1|14|3|15|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|16|3|17|5|X|7|20|8|@]|9|@]|A|$Y|Z]]|$1|18|3|19|5|6|7|21|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|22|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|6|7|23|8|@]|9|@]|A|$]]|$1|1E|3|1B|5|6|7|24|8|@]|9|@]|A|$]]|$1|1F|3|1G|5|6|7|25|8|@]|9|@]|A|$]]|$1|1H|3|-4|5|6|7|26|8|@]|9|@]|A|$]]]|1I|$]]

ALTER COLUMN ID NUMBER worked for me too, but it can be used probably only in case of empty table, otherwise setting back the ID field as Autonumber (ALTER COLUMN ID COUNTER(next ID number here,1)) would not work. At least manually can't be set. 
This is .mdb Access 10 (2002) file put in C://directory/ above any user directory, under Windows XP, opened by Runtime 2010. I have never noticed such behavior when it was inside user directory, like My Documents or Desktop, but maybe this is coincidental and it will occur sometime. It happened first time after few years of using this file with that code.
 
Edited next day: 
It seems to be partially explained. The reason is collating order. The database was created and used previously with this setting: 
Tools > Options > General > New database sort order > Polish 
but in the middletime, this setting in the program was set to > General 
And now it displays that error. It can be fixed easily setting back > Polish 
and running Compact and Repair database (ALTER COLUMN ID COUNTER begins to work again). I have repeat this few times so far and each time it worked. But with General Compact and repair database doesn't help ever.
 
This subroutine:

<pre><code>Private Sub IDProperties()

Dim db As DAO.Database
Dim tdf As DAO.TableDef
Dim TableName As String
Dim i As Integer
Dim str As String

TableName = "the name of table"

Set db = CurrentDb()
Set tdf = db.TableDefs(TableName)

For i = 0 To tdf.Fields("ID").Properties.Count - 1
 On Error Resume Next
 str = str &amp; vbNewLine &amp; tdf.Fields("ID").Properties(i).name
 If Err &gt; 0 Then
 str = str &amp; vbNewLine &amp; Err.Number &amp; " " &amp; Err.Description
 Err.Clear
 End If
 str = str &amp; " = " &amp; tdf.Fields("ID").Properties(i).Value
 If Err &gt; 0 Then str = str &amp; "; " &amp; Err.Number &amp; " " &amp; Err.Description
 On Error GoTo 0
Next
Set tdf = Nothing

db.Close
Set db = Nothing

Debug.Print str

End Sub
</code></pre>

returns i.e. collating order of the ID field. For tables which return 3259 error with sort order = General, ID CollatingOrder = 1045. If such table is deleted and imported a fresh one, ID CollatingOrder = 1033 and 3259 error does not occur. So it seems, that Access changes collating order of the ID field during import. That would be second way to fix that. Or importing entire database to a fresh file. Third way is copying such table - it apparently changes ID's CollatingOrder too. The best would be changing collating order by VBA, but it is read only property.

<pre><code>Private Sub GetCollatingOrder()

Dim db As DAO.Database
Dim tdf As DAO.TableDef
Dim TableName As String

Set db = CurrentDb()
Set tdf = db.TableDefs("table name")

MsgBox "Collating order" &amp; _
 vbNewLine &amp; "- database: " &amp; db.CollatingOrder &amp; _
 vbNewLine &amp; "- table: " &amp; tdf.Fields("ID").Properties("CollatingOrder").Value
 'or tdf.Fields("ID").CollatingOrder

Set tdf = Nothing
db.Close
Set db = Nothing

End Sub
</code></pre>

Only database sort order can be changed:

<pre><code>Application.SetOption "New Database Sort Order", 1033 ' or 1045 for example
</code></pre>

but it changes property of someone's database ... And maybe still compact and repair is required. 
Edited later: 
Now MsgBox shows 1045 for both: General and Polish (and both: db and ID) and stopped displaying error ... Very strange. Maybe because of several compact and repair. 
Edited later: 
Next day again the same error if New database sort order not changed + Compact and Repair. So General stopped working after rebooting. The CollatingOrder property values in the MsgBox are different for ID and entire database before Compact and Repair, the same after Compact and Repair (preceeded by New database sort order change).

blocks|key|3647929|text|我也有同样的问题。显然，这是因为我通过复制已经具有AutoNumber字段的现有表的结构创建了一个新表。不管是什么原因，它在副本上给了我这个错误。在删除该表并从头开始重新创建后，它可以正常工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3647930|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I was having the same problem. Apparently it was because I had created a new table by copying the structure of an existing one that already had an AutoNumber field. For whatever reason it was giving me this error on the copy. It worked after deleting the table and recreating it from scratch.

blocks|key|526798|text|Microsoft+ADO+Ext.2.8+(或6.0+?)为DDL和安全(ADOX)工作!！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|526799|Dim+cat+As+Object
Set+cat+=+CreateObject("ADOX.Catalog")+'late+binding+instead+As+ADOX.Catalog+or+As+New+ADOX.Catalog+to+avoid+using+references+to+ADOX
cat.ActiveConnection+=+CurrentProject.Connection
cat.Tables("Your+table+name").Columns("Your+field+name").Properties("Seed")+=+1
cat.Tables("Your+table+name").Columns.Refresh
Set+cat+=+Nothing|code-block|syntax|javascript|526800|但它很慢，可能是因为延迟绑定。|526801|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Microsoft ADO Ext. 2.8 (or 6.0 ?) for DDL and Security (ADOX) works !!

<pre><code>Dim cat As Object
Set cat = CreateObject("ADOX.Catalog") 'late binding instead As ADOX.Catalog or As New ADOX.Catalog to avoid using references to ADOX
cat.ActiveConnection = CurrentProject.Connection
cat.Tables("Your table name").Columns("Your field name").Properties("Seed") = 1
cat.Tables("Your table name").Columns.Refresh
Set cat = Nothing
</code></pre>

But it is slow, maybe because of late binding.

After re-installing my computer completely, suddenly I get this error: 
<code>Run-time error 3259 invalid field data type on alter table</code> 
when running this query: 
<code>ALTER TABLE Invoices ALTER COLUMN ID COUNTER (1, 1)</code> on a MS Access database.

The data type didn't change, actually nothing changed except for the re-install..

The field ID is a Long Integer field that is set to auto increment for every Invoice that the table holds. Since data resides in this table only temporarily I reset the auto increment after every batch. I think it may have something to do with references missing or changed in different versions.. But I can't seem to figure out which one or why.. 

Do I need to be more explicit in my query? Anyone ever experience this before?

MS Access run-time error 3259 invalid field data type on alter table

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

完全重新安装计算机后，突然出现以下错误：Run-time error 3259 invalid field data type on alter table运行此查询时：MS Access数据库上的ALTER TABLE Invoices ALTER COLUMN ID COUNTER (1, 1)。数据类型没有改变，...

问MS Access运行时错误3259 alter table上的字段数据类型无效
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MS Access运行时错误3259 alter table上的字段数据类型无效EN