Microsoft KB Archive/164453

= ACC97: Errors Converting or Importing with 754 or More Controls =

Article ID: 164453

Article Last Modified on 1/19/2007

-

APPLIES TO


 * Microsoft Access 97 Standard Edition

-



This article was previously published under Q164453



Novice: Requires knowledge of the user interface on single-user computers.



SYMPTOMS
When you use Microsoft Access 97 to convert a database, open a database, or import a form or report created with an earlier version of Microsoft Access, you may receive some or all of the following error messages.

Converting a Database
   Microsoft Access can't open the form.

It contains data that Microsoft Access doesn't recognize. Re-create the form or, if you maintain backup copies of your database, retrieve a copy of the form.

Followed by the message:

There were compilation errors during the conversion or enabling of      this database.

The database has not been saved in a compiled state. The performance of the database will be impaired because Microsoft Access will need to recompile the database for each session. For information on      improving performance, click Help.

Followed by the message:

The Save operation failed.

Followed by the message:

Device I/O error

Opening (Enabling) a Database
  The form or report has too many controls.

Reduce the number of controls on the form or report before using it in this version of Microsoft Access.

Followed by the message:

Invalid operation.

Followed by the message:

There were compilation errors during the conversion or enabling of     this database.

The database has not been saved in a compiled state. The performance of the database will be impaired because Microsoft Access will need to recompile the database for each session. For information on     improving performance, click Help.

Followed by the message:

Unexpected error (32811)

Followed by the message:

The Save operation failed.

Followed by the message:

Unexpected error (32811)

Importing a Form or Report
  The form or report has too many controls.

Followed by the message:

Invalid operation.

-or-

Unexpected error (32811)

When you receive any of these error messages, the object is not imported.



CAUSE
There is at least one form or report in your database that contains a Visual Basic for Applications module and has 754 or more combined controls, sections, and fields in the RecordSource property.



RESOLUTION
Use the version of Microsoft Access with which you originally created the database to modify the design of the form or report. Decrease the total number of sections, controls, and fields in the RecordSource property to fewer than 754.

If the record source for the form or report contains a large number of fields that you do not need to display, consider creating a query that only selects the fields that you need to display, and set it as the RecordSource property for the object.



STATUS
This behavior is by design.



MORE INFORMATION
Microsoft Access 97 limits the total number of controls plus sections plus fields in the RecordSource property to 754. For example, if a form contains a detail section, 500 unbound text boxes, a Visual Basic for Applications module, and a record source that contains 255 fields, you receive the errors listed in the "Symptoms" section when you convert or open the database in Microsoft Access 97. This occurs even though none of the fields in the RecordSource property are actually used on the form.

                 Number of Controls: 500 Number of Sections:  1 Number of Fields in RecordSource: 255 ---                                     756

If a form or report does not contain a Visual Basic for Applications module but does exceed the 754 control limit, the conversion may succeed, but you may receive other errors when you try to design or use the form in Microsoft Access 97.

