ACC1x: Cannot Add Counter Columns to Tables with > 4 MB Data

Last reviewed: May 14, 1997
Article ID: Q97003
The information in this article applies to:
  • Microsoft Access versions 1.0, 1.1

SYMPTOMS

You cannot add Counter data type columns to existing tables containing roughly greater than 4 megabytes (MB) of data.

CAUSE

This problem occurs because of a limitation in the Microsoft Access transaction model, which is limited to a transaction size of about 4 MB.

The problem occurs with Counter columns because the table data for columns is updated when the new column is added. The update takes place in a transaction, and with large tables (greater than 4 MB), the update encounters the Microsoft Access transaction size limit. When this happens, the transaction rolls back and the Counter column is not successfully added.

RESOLUTION

Use the following steps to add a Counter column to a large table:

  1. Copy and paste the table's structure (not the table's data) to a new table.

  2. Add a Counter data type column to the new table.

  3. Create an append query that transfers the data from the old table to the new table.

  4. Verify that the new table has the correct data.

  5. Delete the old table.

  6. Rename the new table to the name of the old table.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access versions 1.0 and 1.1. This problem no longer occurs in Microsoft Access version 2.0.


Keywords : GnlOthr kbusage
Version : 1.0 1.1
Platform : WINDOWS
Hardware : X86
Issue type : kbbug
Resolution Type : kbworkaround


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.