You may encounter errors with your ACCDE/MDE files and/or wizards after installing the March update for Office 2010 (KB3085515)

Issue: After installing the March public update for Office 2010, you may encounter problems with your Access 2010 database files. March 8, 2016, update for Office 2010 https://support.microsoft.com/en-us/kb/3085515 When attempting to launch the Access wizards, you may receive an error.  Examples: This feature isn't installed, or has been disabled. To install this feature, rerun the…

39

Access web apps to be retired

It was announced this week that Access Services is going to be retired. Details of the announcement may be found here:  Updating the Access Services in SharePoint Roadmap Additional timeline information along with possible methods for exporting your data out of an Access web app may be found here: Access web apps no longer supported…

33

Access may encounter a crash after installing the November update KB2837592 or December update KB3114404

Issue: After installing the November or December public updates for Access 2010 or the Click-to-Run updates for Access 2013, Access may encounter a crash while performing a text file import/export. The crash occurs if you click on the Advanced button within the Import/Export wizard. November 10, 2015, update for Office 2010 (KB2837592) https://support.microsoft.com/en-us/kb/2837592 December 8,…

22

How to: Make external connections to an Access Web App

You may want to access the data stored in your Access Web app from other applications. An Access Web App stores its objects and data in a SQL Azure database for SharePoint Online instances or in a local SQL Server for SharePoint on-premise installations. In order to connect to the Access Web app data on…

19

Errors executing or saving data macro with SendEmail action in Access web app on SharePoint Online

Issue: You may encounter errors executing or saving data macros that use the SendEmail macro action in an Access web application on SharePoint Online. Errors: Invalid field name 'ID' Invalid object name 'Inserted' Cause: This is a product issue. Work Arounds: You may try any of the following options to work around the issue: 1. If the…

12

Access Web App error "We couldn't retrieve the items to list here"

We are receiving reports that many users are encountering an error "An error occurred. We couldn't retrieve the items to list here." when navigating views in their Access Web app on Office 365 (O365). The Access developers are aware of the problem, a fix has been made and is rolling out. Most tenants will be fixed this evening. A…

10

Access app: Restrict editing records by user

The following example demonstrates how to toggle the enabled property for the edit/delete action bar buttons on a form/view in relation to the current user.   Within SharePoint, create a new Access app In the Add Tables, search for and select the Orders template   Create a Data Macro to lookup the employee’s ID based…

7

Unexpected autonumber jump in Access apps

We’ve received reports from customers that occasionally their Access app autonumber field jumps by an unexpected number. For example, you may have an ID field that is sequential from 1 to 83 but then the ID suddenly jumps to seemingly random number like 1075. The autonumber is meant to guarantee a unique record identifier larger…

5

Errors working with Access 2010 web databases on SharePoint Online

Issue: When attempting to open an Access 2010 web database within a SharePoint Online environment, you may receive one of the following error messages: “Site is down” Or “An error has occurred” Or “Failed to evaluate expression ‘<expression>’   Status/Resolution: The Product Group has reported that this issue should now be resolved for all tenants. In…

3

Access Web App error "403 Forbidden"

A number of existing Access Web Apps are reporting an error "403 Forbidden" when you attempt to view them from an Internet browser and "Server was unable to process request —> Only users who can View Pages can list Apps." when used from the Access client. This issue was resolved Saturday, June 7th at approximately…

3