Microsoft Access Version Releases, Service Packs, Hotfixes, and Updates History

• An option to configure Jet Red Database Engine and Access Connectivity Engine to block access to remote databases. This has been added to make applications more secure and allow users to disable remote references in query execution. For more information, visit Microsoft's page Configure Jet Red Database Engine and Access Connectivity Engine to block access to remote databases.

  Note: Installing this update does not make changes to the Jet Red Database Engine or the Access Connectivity Engine (ACE).

This update adds security enhancements for Access that provide a more secure version of the signature scheme for Visual Basic for Applications (VBA) projects.

Note: To make this improvement to take effect in Access, you have to install KB4493153 and KB4493225 together with this update.

This update fixes the following issues:

• The form running code in the main Access window was not visible when the application was stopped at a VBA breakpoint or Stop statement.
• New reliability improvements to the Visual Basic for Applications (VBA) projects

Note: To enable this improvement, you have to install KB4493157 together with this update. If you do not update the KB4493157, you may not run VBA Project newly signed in a 32-bit version of Access on a 64-bit version of Access and vice versa.

This security update resolves a remote code execution vulnerability that exists in Microsoft Access, when the user opens a file that contains a malformed graphic image or inserts a malformed graphic image into an Office file.

This security update fixed the following issue:

• A remote code execution vulnerability exists when Microsoft Office improperly loads arbitrary type libraries.

This update fixes an issue that can cause Microsoft Access to fail to identify an Identity Column in a linked SQL Server table, which can cause rows to be reported as deleted incorrectly.

For more information, see Access does not recognize the Identity Column in a linked SQL Server table.

Be aware that this update applies to the Microsoft Installer (.msi)-based edition of Office 2016. It doesn't apply to the Office 2016 Click-to-Run editions, such as Microsoft Office 365 Home.

This update fixes the following issue:

• After you install update KB3085368 or KB4484113, you may receive the following error message when you try to run an Update query in Microsoft Access: Query "query name" is corrupt.

• Access crashes when a form ahs code behind the Resize even that references for the Form.Recordset property.
• Changes to a macro may not be saved if you don't change focus after making a change.

• This update fixes the following issue where you may experience crashes in Access 2016 when you open views in non-design mode, such as in Datasheet View, FormView, Layout View and Report View.

• In certain circumstances, data that's linked to a SharePoint list is displayed as "#Deleted" in Access 2016.

• When you view a form that contains a modern chart inside a tab control, Access 2016 crashes.

• Improvements to enable the new Japanese era when it is available.
• Fixes an Access 2016 crash issue that occurs when a form that contains a modern chart in a tab control is loaded in an Access database.

This security update resolves vulnerabilities in Microsoft Office that could allow remote code execution if a user opens a specially crafted Office file. To learn more about these vulnerabilities, see Microsoft Common Vulnerabilities and Exposures CVE-2018-8312.

• Access 2016 may freeze when you try to connect to a list on a SharePoint site.

This security update resolves vulnerabilities in Microsoft Office that could allow remote code execution if a user opens a specially crafted Office file. To learn more about these vulnerabilities, see Microsoft Common Vulnerabilities and Exposures CVE-2018-0903.

• When you open a password-protected Access runtime application, the Home tab shows in the ribbon while the password dialog is up.
• Access 2016 may crash when you try to add a lookup column to a related table in the Datasheet view.

This update improves the translation of Allow Full Menus option for the Danish version of Access 2016.

• You receive an error message when you import data from a SharePoint list while you use the sr-Cyrl-RS language pack.

• MSACCESS.EXE continues to run after close if accessibility tool or any application that requests an accessible interface is running.

Fixes applications that use the Access runtime close unexpectedly when you export a report to PDF.

Enable you to import and export data in dBase.

Fixes the keyboard support for Office add-ins in the Backstage.

• When you try to set properties of an ActiveX Data Objects (ADO) record set by using some Visual Basic codes in an Access 2016 form, you receive an error message.

• Can't set the Field Size property for number fields in Table Design view.

• When you drag an object from the Navigation pane to the macro designer in Access 2016, Access 2016 crashes.

• When you try to insert an app in Office 2016 applications, not only the apps for Office 2016 but also the apps for Office 2013 are displayed.

• When you use the Max aggregate function in a query in Access 2016 that has the Polish language enabled, you receive the following error message: "Nie zdefiniowana funkcja 'Maksimum' ".

• When you double-click certain action items in the Action Catalog panel in an Access Web App, the Access Web App may crash.
• After you change and save a query in SQL view for a database in Access 2016, the query's SQL text disappears.
• When you link a Microsoft SharePoint list to an Access App, you receive the following error message:
  "An error occurred in the client while attempting to communicate with the server."

• VBA Library names aren't updated to reflect Access 2016. This update changes the version number for Access object library.
• After you copy, paste, or import forms and reports in Access 2016, the color property settings of existing themes are changes.
• New Serbian locale (sr-latn-rs) is added to replace the existing locale (sr-latn-cs).
• After you set the OverrideDisableAllActiveX Group Policy setting, you can't run the trusted WebBrowser ActiveX control or import wizard in Access 2010 even though you set the DisableAllActiveX Group Policy setting.
  
  Additionally, you receive the following error message in the import wizard:
  There is no object in this control.
  
  Note that the "DisableAllActiveX" registry key is located in the following path:
  HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\Common\Security

• An option to configure Jet Red Database Engine and Access Connectivity Engine to block access to remote databases. This has been added to make applications more secure and allow users to disable remote references in query execution. For more information, visit Microsoft's page Configure Jet Red Database Engine and Access Connectivity Engine to block access to remote databases.

  Note: Installing this update does not make changes to the Jet Red Database Engine or the Access Connectivity Engine (ACE).

This security update resolves a remote code execution vulnerability that exists in Microsoft Access, when the user opens a file that contains a malformed graphic image or inserts a malformed graphic image into an Office file.

This security update fixed the following issue:

• A remote code execution vulnerability exists when Microsoft Office improperly loads arbitrary type libraries.

• After you install update KB4484119, you may receive the following error message when you try to run an Update query in Microsoft Access: Query "query name" is corrupt.

• An attacker can exploit the vulnerability by providing a specially crafted document file designed to exploit the vulnerability and then convince a user to open the document file. The security update addresses the vulnerability by correcting how Microsoft Access handles objects in the memory. To learn more about these vulnerabilities, see Microsoft Access Remote Code Execution Vulnerability CVE-2018-8312.

• A remote code execution vulnerability exists in Microsoft Access software when the software fails to properly handle objects in memory. Exploitation of the vulnerability requires that a user open a specially crafted file with an affected version of Microsoft Access. To learn more about these vulnerabilities, see Microsoft Access Remote Code Execution Vulnerability CVE-2018-0903.

• Access 2013 is unable to start if it's installed side by side with Office 2016 applications.

• When you use the Web Browser control on an Access 2013 form, conditional formatting that's applied to other controls may not be applied correctly.

• When you use the Max aggregate function in a query in Access 2013 that has the Polish language enabled, you receive the following error message: "Nie zdefiniowana funkcja 'Maksimum' ".

• Assume that you try to export a table to a text file in Access 2013. When you select the [Advanced] button the Export Text Wizard dialog box, Access 2013 may crash.

• Fixed inability to calculate some fields in if the computer hasn't been restarted for a long time (24 days, for example), and after you change and save a query in the SQL view for a database in Access 2013, the query's SQL text disappears.

• When you link a Microsoft SharePoint list to an Access app, you receive the following error message:
  An error occurred in the client while attempting to communicate with the server.
• After you set the OverrideDisableAllActiveX Group Policy setting, you can't run the trusted WebBrowser ActiveX control or import wizard in Access 2010 even though you set the DisableAllActiveX Group Policy setting.
  
  Additionally, you receive the following error message in the import wizard:
  There is no object in this control.
  
  Note that the "DisableAllActiveX" registry key is located in the following path:
  HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\Common\Security

• Enables single sign-on (SSO) for ADAL on cloud domain-joined computers. On cloud domain-joined computer that has Modern Authentication enabled, domain accounts seem to be logged in but can't open files.
• When you try to use the import text wizard to import a text file that contains DBCS characters in Access 2013, the results don't align correctly for newly created columns.

• When you start Access 2013 on a computer that was not restarted for a long time (for example, 24 days), the CPU usage of the MSACCESS.EXE process becomes high. However, applying this update will reintroduce the problem that is addressed by the March 10, 2015, update for Access 2013 (KB2956176). As soon as this update is installed, fields that are bound to expressions on forms may not be recalculated when the computer has not been restarted for a long time.

• Opening multiple objects in design view and then try to switch to another view in Access 2013, Access 2013 may become unresponsive.
• When you undo a column deletion operation in table design view in Access 2013, Access 2013 crashes.
• The Conditional Formatting button does not work if the ribbon is collapsed in Access 2013.
• After you import a form or report or you copy and paste an existing form or report in an Access app, the theme colors are changed unexpectedly under the control of the newly created form or report.

• When you try to split a database by using the Access Database function in Microsoft Access 2103, Microsoft Access Signed Package (.accdc) is the only save type and the Access Database (.accdb) save type is unavailable.

• When you use Visual Basic for Applications (VBA) languages to update the value of a combo box or a list that has a record source on Access 2013 form, Access 2013 crashes.

• You may be unable to calculate some fields in Access 2013 if the computer has not been restarted for a long time (24 days, for example).
• When you open an Access Web App that contains very large data macros in Access 2013, you may receive an error message that resembles the following:
  There was a problem accessing a property or method of the OLE object.
• When you try to delete multiple columns from a table in Access 2013, Access may crash.
• Assume that you create an Access Web App in Access 213. An error may occur when you save the Web App in the following scenarios:
  • You add a new field, then you set the Index property to Yes (No Duplicates), then set the data type to Image.
  • You add more than 32 new fields and then set the Index properties to Yes (No Duplicates).
  After, in this scenario, when you try to open the saved Web App, the error occurs again.
• Updates Access 2013 to work correctly with design changes that were made to the Microsoft Forms ActiveX Control (FM20.dll) shared component library. For more information, see the following Microsoft Knowledge Base article: "Cannot insert object" error in an ActiveX custom Office solution after you install the MS14-082 security update (KB3025036).

• When you click [OK] in the Print dialog box to print a file, the printing does not start. You have to click [OK] again to start printing. This issue occurs on a Windows 7 or Windows Server 2008 Service Pack 2 (SP2)-based computer that has the Japanese Microsoft IME enabled in the language control panel.

• If Portuguese (Brazil) is the default display language for Access 2013, open the Visual Basic Editor, and click [Tools] > References. When you click the [Browse] button in the References dialog box, Access may crash.

• VBA error codes in the range of 7865 to 7899 are off by one. For example, when you try to delete a nonexistent object by invoking the DoCmd DeleteObject method, you receive an error code 7873 instead of 7874.

• When you try to set properties of an ActiveX Data Objects (ADO) recordset by using some Visual Basic code in an Access 2013 form, you receive one of the following error messages.
  • Run-Time error '2455'. You entered an expression that has an invalid reference to the property UniqueTable
    The expression <event> you entered as an event property setting produced the following error: "Type Mismatch (Run-Time error 13)".
• When you try to package an Access Web application, an .app file is not generated and you receive the following error message:
  • An error occurred in the client while attempting to communicate with the server '[URL]'. Please contact your system administrator or technical support.

• Previously unreleased fixes that are included in this service pack. In addition to general product fixes, these fixes include improvements in stability, performance and security.
• All the monthly security updates that were released through January 2014 and all the Cumulative Updates that were released through December 2013.

This security update resolves a remote code execution vulnerability that exists in Microsoft Access, when the user opens a file that contains a malformed graphic image or inserts a malformed graphic image into an Office file.

This security update fixed the following issue:

• A remote code execution vulnerability exists when Microsoft Office improperly loads arbitrary type libraries.

This update fixes the following issue:

• After you install update KB4484127, you may receive the following error message when you try to run an Update query in Microsoft Access: Query "query name" is corrupt.

Be aware that this update applies to the Microsoft Installer (.msi)-based edition of Office 2010. It doesn't apply to the Office 2010 Click-to -Run editions, such as Microsoft Office 365 Home.

• Adds support for new Japanese eras in the Japanese calendar. Note: To enable this improvement, you must install December 4, 2018, update for Office 2010 (KB4461579) together with this update.
• Fixed - After KB4461614 is applied, Access 2010 and Excel 2010 stop working.

After you install this security update, Microsoft Access 2010 and Excel 2010 stop working.

To resolve this issue, install January 18, 2019, update for Office 2010 (KB4462157).

This Office Update is no longer available from the Microsoft Update or the Microsoft Download Center. After you install this update, you may not be able to open Microsoft Visual Basic-enabled apps in Microsoft Access 2010. Also, Access wizards may not run. To work around the problem, uninstall this update by following the steps in the "How to uninstall this update" section.

If you installed it, visit our blog post Microsoft Office 2010 Update KB3085515 Causes Access ACCDE and MDE Databases to Crash.

• After you set the OverrideDisableAllActiveX Group Policy setting, you can't run the trusted WebBrowser ActiveX control or import wizard in Access 2010 even though you set the DisableAllActiveX Group Policy setting.
  
  Additionally, you receive the following error message in the import wizard:
  There is no object in this control.
  
  This issue occurs after you apply the March 10, 2015 update for Access 2010 (KB2837601). The Group Policy setting is set under the following registry key:
  HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\Common\Security

• You may be unable to calculate some fields in Access 2010 if the computer hasn't been restarted for a long time (24 days, for example). This issue occurs after you apply the July 14, 2015, update for Access 2010 (KB2965300).

• When you start Microsoft Access 2010 on a computer that has not been restarted for a long time (for example, 24 days), the CPU usage of the MSACCESS.EXE process becomes high. However, applying this update will reintroduce the problem that is addressed by the Hotfix KB2899528 for Access 2010 November 11, 2014. As soon as this update is installed, fields that are bound to expressions on forms may not be recalculated when the computer has not been restarted for a long time.

• Updates Access 2010 to work correctly with design changes that were made to the Microsoft Forms ActiveX Control (FM20.dll) shared component library. For more information, see the following Microsoft Knowledge Base article "Cannot insert object" error in an ActiveX custom Office solution after you install the MS14-082 Security Update (KB3025036).

• Issues that may arise for a PC running Access for more than 20 days. Access may consume excessive CPU resources. Background tasks do not execute. Calculated fields and domain functions (DLookup, DSum, DCount, etc.) do not display a value.

• Security vulnerabilities in Microsoft Access that could allow remote code execution when a specially crafted Access file is opened.

• When you insert an EPS image into a database by using the Insert and Link option in the Insert Picture dialog box in Access 2010, the image is not embedded.

• Previously unreleased fixes that are included in this service pack. In addition to general product fixes, these fixes include improvements in stability, performance and security.
• All the public updates that were released through May 2013 and all the cumulative updates that were released through April 2013.

• When you import and Excel workbook that contains currency data into Access 2010, the currency data is not imported.
• Assure that the drivers that are included in Microsoft Office 2010 or Access Database Engine 2010 are installed on a computer. You create an Excel spreadsheet that contains a data connection to an Access database on the computer. When you open the spreadsheet in Microsoft Excel 2007 and then update the data in the spreadsheet, you receive the following error message: "Could not find installable ISAM".
  
  This issue also occurs if you create the spreadsheet in Excel 2013 and then open the spreadsheet in Excel 2010.

• ADO-based applications that are compiled in Windows 7 SP1 or in Windows Server 2008 RS SP1 use the new interface identifiers (IIDS) in the ADO type libraries that were included in the SP1 packages for Windows 7 and for Windows Server 2008 R2.
• This issue does not occur if the hotfix that is described in the following Microsoft Knowledge Base article is installed on the computer that is running an earlier version of Windows:
  • For more information, see Microsoft's page "Type Mismatch" error message when you run a VBA macro in a 64-bit version of an Office 2010 application (KB983246).

• Resolves vulnerabilities in the 2007 Office suite that could allow remote code execution if a user opens a specially crafted Office file.

• Access hanging on large attached table when clicking arrow beside date column.
• Templates disappear (with Spanish MUI on Win XP/2003).
• Unable to link Sybase database if File DSN contains spaces.

• Errors when importing data using the "Get External Data - Text File" wizard.

• ApplyFilter macro does not accept subsequent parameters, and "There isn't enough memory to undo......" error when running 1.5MB query.

• Fixes Runtime crash after application of Service Pack 2.

• Ribbon options for rich text box now work in subforms.

• Office 2007 SP2 failure to update.
• Some files objects can be deleted from the Navigation Pane even if you do not have permission.
• Combo Box becomes transparent when losing focus.

• Parameter shown as numbers (ASCII Value) instead of text on a report.
• Store procedure executed multiple times when opening a form/report.
• Navigation Pane and Status Bar issues after applying Service Pack 2.
• Calculated Field changes value while scrolling.

• Query crashing (ODBC, Inheritance and Aggregation).
• Last Row not imported.
• Decimal Lookup field not displayed (from ODBC table).

• Reports not showing all CAD images from the Attachment field. Also fixes the continuously flickering screen when you open a report that contains a graphic chart in Report View or Layout view.

• Slow performance when clicking fields, tabbing between fields or scrolling down through fields in Datasheet view.

• Fixes Open Snapshot so that snapshots open more reliably, even if there is no SharePoint root site.
• Display issues that cause calculations to appear incorrect in some cases.
• Fixes the Import data wizards, report printing and previewing, macros, Excel integration, and date filters.
• Fixes conditional formatting in Mozilla Firefox browsers.

• Exports reports to Excel.
• PDF Exporting feature is now built in.
• Supports memo fields in the mailing label wizard for addresses.
• Improves connections to cubes by using .odc files in non-English cases.
• Improves the performance of programmatic scenarios.
• Improves support for generating Excel Web Access Web parts on new sites.
• Recognizes trusted locations set at the machine level.

• 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.

• Running 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.

• When 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.

• Runtime Error 3251 Operation is not supported for this type of object: When using Data Access Object (DAO) code to synchronize a replicated Access 2007 database.
• Runtime Error 3001 Invalid argument: When using a Microsoft Visual Basic for Applications (VBA) macro in Access 2007 to update records in a Microsoft Jet 3.x database.

• Problems with SP3 such as combo box and list box displaying no value or incorrect values.
• Working with bit fields in SQL Server tables.
• Prevent unexpected closing.
• Address problems with ADPs and VSS and other issues.