Article ID: 128221 - View products that this article applies to.
This article was previously published under Q128221
Moderate: Requires basic macro, coding, and interoperability skills.
When you save a table after you add a new field or change the properties of an existing field, you receive the message "Too many fields defined," followed by the message "Errors were encountered during save. Data types were not changed." You receive these messages even though you have 255 or fewer fields defined in the table.
NOTE: You also receive this message if you add or modify fields in a report that is based on a table that has too many fields.
NOTE: This error message generates the Microsoft Jet Database Engine 3.0 Reserved Error number 3190.
This article assumes that you are familiar with Visual Basic for Applications and with creating Microsoft Access applications using the programming tools provided with Microsoft Access. For more information about Visual Basic for Applications, please refer to your version of the "Building Applications with Microsoft Access" manual.
NOTE: Visual Basic for Applications is called Access Basic in Microsoft Access versions 1.x and 2.0. For more information about Access Basic, please refer to the "Introduction to Programming" manual in Microsoft Access version 1.x or the "Building Applications" manual in Microsoft Access version 2.0
The internal column count that Microsoft Access uses to track the number of fields in the table has reached 255, even though you may have fewer than 255 fields in the table. This can happen because Microsoft Access does not change the internal column count when you delete a field. Microsoft Access also creates a new field (increasing the internal column count by 1) for every field whose properties you modify.
To free the internal column count for deleted fields or for fields whose properties you modify, do one of the following:
In Microsoft Access, you can define up to 255 fields in a table. If you create 255 fields and then delete 10, Microsoft Access does not release the fields from the internal column count. Also, for every field whose properties you modify, Microsoft Access creates a new field and does not release the original field from the internal column count.
Steps to Reproduce BehaviorNOTE: For Microsoft Access version 1.x, manually create a table with 255 fields, all with a data type of Text. The code below works only for Microsoft Access 2.0 and later.
For more information about table specifications, search the Help Index for specifications, or ask the Microsoft Access 97 Office Assistant.
Article ID: 128221 - Last Review: January 19, 2007 - Revision: 2.3
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Contact us for more help