The Access client is still used to create and design tables, views, macros, and more. End-users will use a browser when interacting with the Access AppSQL rendered as .net app in SP. Apps are saved as a package and published in the app store. An Access web app is a new type of database that you build in Access, then use and share with others as a SharePoint app in a web browser. To build an app, you just select the type of data you want to track (e.g., contacts, tasks, projects, etc.). Access creates the database structure (SQL) complete with views that let you add and edit data. Navigation and basic commands are built-in, so you can start using your app right away.
Our Take: Our experience with large lists in SharePoint typically leads to creating custom
databases that house these large lists and a developmental structure to support them. This is primarily because a SharePoint content database can’t handle heavy loads on large lists. For this reason, Microsoft created a resource throttling view for large lists starting at just 5k records for regular users. For admins, the number of records is much
higher. In SharePoint, the ever increasing demand of large list creation and use would require Microsoft to come up with a solution to assist this demand—and that would either increase resource limits or require another approach. The Access Services solution provides both the scale and flexibility you would expect from utilizing SharePoint to function in this manner.
Stay tuned as we release more of this 11-part series from our whitepaper on SharePoint 2013′s newest features right here on our blog for your reading pleasure. But, why wait? You can download the whitepaper in its entirety now.
Let us know your comments, questions and conerns as you read through the document.