"#Error" is displayed in the output when you print a report that has an expression in Design View.

A Click event on a form reports the wrong record until the event ends.

A licensed ActiveX control cannot open in Access 2007 when the .lic file is renamed or does not exist. The .lic file is only required to insert the control and does not need to be present on the machines that the database is deployed to.

A passthough query is executed twice when the query is saved.

A run-time error occurs when you set any position property (top, left, height, or width) of a control in the OnFormat event.

A StopMacro action in a macro that is looping through the use of the repeat expression argument in the RunMacro action will cause all pending iterations of the macro to end.

A user can only see the first 4,750 tables of an SQL database in the ODBC import dialog box.

A user cannot add, edit, or delete records to a subform in an ADP that is based on a multi-table view or stored procedure unless the user specified the unique table property for each table.

A user creates a query, and then saves it in SQL view. When the user opens a form with the query in a subform, the user finds that the query has been deleted.

Access crashes when a parent form sets its child's source on its own current event after the parent's source is set in the Open event.

After a user opens a Filter drop-down list in a subform datasheet, an error message occurs because of invalid bracketing.

After you try to insert a record on the one side of a many-to-one relationship in Datasheet view, the table on the one side may get into a state where records can no longer be added.

An empty control source in a form causes the open form command button wizard to display an empty list box for filtering.

An error prompt appears when a user runs the ApplyFilter command with a non-existent object specified.

Applying Microsoft Security Bulletin MS08-028 may cause a benign corruption error in multi-user databases.

Customized Quick Access Toolbar (QAT) buttons do not appear unless you open the database through the Most Recently Used list (MRU) in Getting Started.

Dates without a delimiter (yyyymmdd) are not converted correctly when you import text.

Exporting to PDF/XPS or SNP fails when executing code that is referenced in another database.

If you use the data collection feature to update a row that does not exist when the data collection reply is processed, the first row is updated, and you do not receive an error message.

In Internet Explorer 8, you cannot use a mouse to select multiple cells in Microsoft Office Access Web Datasheet.

In some edge cases, a casual exploration of the Getting Started experience can lead to the Getting Started experience no longer displaying a list of templates.

Macros that use the SetProperty action to run in context in subforms or subreports cannot be authored.

Memo fields are not included in the available fields for the Mailing Label Wizard.

Numbers and dates are displayed as "####" for vertical text boxes in Report Print Preview.

On a computer that uses Windows XP theming, a check box that uses the Tristate property does not function correctly and seems to be unselected.

OpenForm does not apply filter criteria if the form is already open.

Records in nested subforms cannot be deleted.

Relinking a table fails if the table contains an AppendOnly memo field.

Templates created with complex data (multivalue fields or attachments) instantiate with failures.

The "More Smart Tags" button opens the incorrect URL for non-English versions of Access.

The Keep Together property is ignored when a user has a report with an invisible detail section and group headers that have the Repeat property set to true.

The Next Week, This Week, and Last Week date filters are broken in non-English versions of Office.

The wizard that generates the where condition of an open form macro does not put '=' in front of an expression.

Unsafe function names in expressions are not translated into local languages and are displayed in English.

When a user deletes a column in a Design Master and then tries to synchronize with a replica, the synchronization fails.

When a user deletes a record and then chooses to undo the change in the Run view of the form, the user is prompted to save the form.

When a user exports a query that needs Name Fixup performed, the query is permanently replaced with an empty query, and the export fails.

When a user exports to the RTF format, the export is much slower than O11 for linked data sources.

When a user imports a text file that has fewer columns than the table it will be added to, the default value is not applied.

When a user imports a text file with delimited text, the import fails if the file is bigger than 32 KB.

When a user selects the fixed width setting and then modifies the column widths to export the text, the customized width setting is ignored, and the default width is used.

When an ApplyFilter action is on the Open event, Access crashes when you switch from Design view to Report view or Layout view for a report.

When subform records are deleted by using code and warnings are suppressed, Access hangs when it tries to commit a JET transaction that has not been opened.

When the OnError action runs as part of an AutoKeys macro and the AutoKeys key sequence is pressed, the Access Runtime crashes.

When using Ace OLEDB to execute a parameterized query and pass in different parameter values, the Execute method will use the same parameter length as the first parameter.

When you add a record in Access JPN for continuous forms, the first character is lost.

When you add a total at a subReport with a datasource pointing to a field in the parent report, the control source is used for the name that contains the expression (data source) instead of the valid name.

When you change the record source of a form in Browse View, unbound controls may lose their data.

When you create a table with a primary key that is not called “PrimaryKey” and you enter data in the star column or in a newly inserted column in a row other than the first row, you may receive an error, and the data will not be entered in the correct row.

When you open a linked table from Outlook, Access crashes.

When you open a report using Visual Basic and then try to export the report, Access crashes.

When you quick create a form with a hyperlink field, the hyperlink property is not set.

When you start the Query Builder from the property sheet for a form or report, the property sheet closes while the Query Builder is open, and changes to the query are lost.

When you try to import an .xlsx or .xlsx file by using the SQL Server 2005 Import Wizard, the ACE OLEDB provider hangs.

When you try to save a form or a report after you change a textbox to a label, Access crashes.

You cannot run Domain Aggregate functions against linked text files by using the "/cmd" switch.

When you try to use Data Access Object (DAO) code to synchronize a replicated Access 2007 database, you receive the following error message: Run-time error '3251': Operation is not supported for this type of object.

When you use a Microsoft Visual Basic for Applications (VBA) macro in Access 2007 to update records in a Microsoft Jet 3.x database, you receive the following runtime error message: Run-time error '3001': Invalid argument

In Access 2007, you open a Microsoft Office Access 2003 database that contains a custom shortcut menu for a subform. Then, you right-click the subform. When you do this, the default shortcut menu is displayed instead of the custom shortcut menu

When you try to run a Microsoft Access project (.adp) in Access 2007, the project may run slowly. Or, the project may take longer than expected to respond to actions that are performed on the project

You close or compact and then close an Access 2007 database. Then, you reopen the database. After you do this, you cannot use some menus or some menu items.

When you click the Add New Field column in the main datasheet, Access 2007 does not take focus out of its subdatasheet. Therefore, the data type of the most recently focused column in the subdatasheet is changed when you try to add a new column to the main datasheet by using the Data Type drop-down box.

When you use the Label Wizard in Access 2007, you receive a security prompt. If you click OK on the security prompt, you receive an error message. If you click Yes on the error message, you are returned to the Label Wizard. When you try to finish the wizard again, you may receive another error message.

In Access 2007, you receive the following error message when you try to execute a query that contains parameters:

Access 2007 returns only the first page of records from a User Information table. The first page of records contains no more than 2,000 records.

In Access 2007, the page controls for the transparent tab are not transparent. This issue occurs on any Microsoft operating system, such as Windows Vista or Windows XP, that has themes turned on and enabled by default.

You install Access 2007 and Microsoft Office Access 2003 on the same computer. When you run Access 2007 after you run Access 2003, Access 2007 takes several minutes to repair itself.

After you run an update query that sets an AutoNumber field to Null in Access 2007, and then you compact the database, you can still update the AutoNumber field data. This issue may result in the loss of data. After you compact the database, the MSysCompactError table is created. This change should remove the ability to update AutoNumber fields.

When you open a form that is bound to a Microsoft Office SharePoint table, it is possible to add data to the form. However, when the form is closed, the data is lost. This behavior does not allow you to add data to a form in a read-only database in Access 2007. The form is bound to a SharePoint table.

When you open a custom shortcut menu bar in a form in Access 2007, the shortcut menu is missing. Additionally, you may receive an error message that says that the shortcut menu does not exist when you open the database again.

When you import Outlook contacts into Access 2007, unexpected characters may appear on the Mail Merge Recipients dialog box This problem occurs when the Outlook contacts contain some Romanian characters.

Fields that are bound to time-intensive expressions appear blank in Access 2007. These fields are empty until you click the textbox or until you click anything outside of Access 2007 if the following conditions are true: • The Control Source property of a textbox uses the DLookup() function.  • The query that is called by the DLookup() fuction references a control on a form.

Text fields are detected as memo fields when you paste some text fields from Microsoft Office Excel to Access 2007. When Access 2007 detects columns that have fewer than 255 characters, "fields of type" text is created.

This issue also occurs in any language version of Access 2007 that has the Bulgarian regional setting enabled.

When you programmatically select an item in a List box on a form, the selected item does not become visible if it was not visible before you selected it in Access 2007.

In Access 2007, the click event for an image control does not work when the image control is inside a tab control.

You cannot use the OpenRecordset function to open some DAO database objects through Open Database Connectivity (ODBC) connections in Access 2007

The behaviors of the StopAllMacros macro action and the StopMacro macro action are swapped in Access 2007.

You create a macro that uses the DoCmd.SelectObject method to select an object in the database by name. If you specify the name of an object that does not exist in the database, you do not receive an error message. Additionally, nothing happens.

When you try to import a large .CSV file, such as a file that is larger than 30 megabytes (MB),, Access 2007 appears to stop responding at the import dialog box. After a few moments, you may receive the following error message: "File sharing lock count exceeded. Increase MaxLocksPerFile registry Entry"   When you click OK to close the error message, you can usually finish the import process. All records are imported successfully.

When you import data from an Excel spread sheet into Access 2007 by using the long integer data type, the number 1 is incorrectly added to some numbers.

In Access2007, the modified date that is displayed in the Navigation Pane for all objects, except tables and queries, is never updated.

When you try to convert an .accdb file to an .mdb file, nothing happens. No error message appears.

When you change the Enabled property of a checkbox on a form by running a macro that uses the SetValue action, you may receive the following message when the sandbox is enabled: Access failed to evaluate one or more expressions because 'Enabled' was referenced in an expression. Only functions and properties that are considered to be safe are allowed in expressions when Access runs in sandbox mode. For more information on sandbox mode, search for "Sandbox mode" in Access Help.

When you open a database in runtime mode, the floating UI for attachment controls and for formatting in rich-text enabled fields is not displayed correctly.

When you update referenced cells, you update the literal cell address instead of the referenced cell. This issue occurs when you update Excel data through the ISAM programatically.

When you try to delete multiple objects by using the delete option on the context menu, database objects that were not selected may be incorrectly deleted.

You cannot use code that uses the index of the item in a list box to set the selection.

If you send an "update existing data" e-mail message that contains a Yes field and a Nofield, a system that uses non-English language settings cannot process replies to the message. This is true if the user does not manually localize the value within the "Yes/No" field. Additionally, the "yes" string and the "no" string are not localized when you create an HTML Data Collection form that contains a boolean field.

When you try to delete a record in a sub-form that is embedded in a main form, the row is longer displayed. However, the record is actually not deleted. If you press F9 after you delete a row in the sub-form, you will receive the following error message: Operation not supported in transactions

When you add an attachment field to a table, you may receive the following error message: The Microsoft Office Access database engine could not find the object. Make sure the object exists and that you spell its name and the path name correctly. This issue occurs when the field has a union query that has more than one union on tables with complex data.

When you set the data type of a new field to a non-text type, such as Attachment, in the Datasheet view, Access 2007 may stop responding

When you return to the property sheet after you change the RecordSource property, Access 2007 may stop responding The issue can occur after you click Builder in the property sheet to open the QBE.