Beginning SharePoint 2013 Development

WHAT’S NEW IN ACCESS SERVICES

Access Services has moved forward significantly on its continuous innovation trajectory with this release. Access Services has a redesigned architecture around the new cloud app model so with the Microsoft Access rich client you now create apps for SharePoint. Apps for SharePoint can be deployed to the on-premises SharePoint or Office 365 SharePoint Online corporate catalog for apps and can be published to the SharePoint Store on Office.com for worldwide availability.

In SharePoint 2010 you used the Access client to create and publish Web databases to SharePoint. The publishing process generated native SharePoint artifacts: Access tables became SharePoint lists, forms became .aspx pages, data macros became workflows, UI macros became JavaScript, and so forth. This deployment model benefited end users in that they could create their point, data-centric solutions and make them available to their colleagues via SharePoint. Any colleague, located anywhere in the world with access to SharePoint, could use the Web-based solution without needing the Access client. For updates to the UI and modifications to the database structure, the Web database owner used the Access client to make the changes and then simply republished the Web database to SharePoint and the updates were immediately available.

With Access and Access Services 2013 and the advent of the new cloud app model come two significant changes. One change is that SharePoint is no longer the target ...