> are you saying that once a field is created, neither its Type or
> Attributes properties can be modified?
Well, per DAO help file, Type is read-only once the field is appended (so,
no, it can't be modified), but Attributes is *supposed* to be read-write
when the appended Field object is associated with a TableDef. I'm a little
surprised at that, since experience says otherwise: Even if it's just a
regular numeric field (i.e., not AutoNumber), you'll get an Invalid
Operation if you try to reset the Attribute property to anything, even it's
default of 0.
Perhaps Attribute and Type are just so intertwined in some cases (like this)
that Attribute becomes read-only. I don't know. I do know that creating a
new field and updating "old" data to it would be a work around.
but maybe a MVP will contribute their thoughts on the subject...
HTH,

Signature
George Nicholson
Remove 'Junk' from return address.
> When I created the field, the autonumber was added by using the attribute
> property, as shown below;
[quoted text clipped - 40 lines]
>> > set tdf=currentdb.tabledefs("Table1)
>> > tdf.Fields("Autonumfield").Attributes = dbFixedField