Microsoft Office Tutorials and References
In Depth Information
Building a Custom Web App
By linking tables to a SharePoint site, you can create front ends for an
existing SharePoint site or give users access to data from your database in
SharePoint. These users don’t even have to have Microsoft Office Access
installed to edit the data in a SharePoint list; they just need access to the list
on the SharePoint site.
Building a Custom Web App
If you work through Chapters 1 and 2 of this minibook, you see how to
create a rich, data-driven Windows application that you or your company
can use to track all kinds of information. One day, you can build a database
that tracks your music collection at home, and the next day, you can work
on a database that tracks sensitive corporate data (so that you can continue
to finance a music collection that’s large enough to require a database).
Like many Access developers before you, you’re probably thinking, “Wow, it
would be great to put this database online so I can access it from anywhere.”
With the release of Microsoft Access 2013 and SharePoint 2013, you can.
This capability comes at a cost, however: You have some limitations on the
formatting and structure of the database. The first big limitation is that you
must use SharePoint 2013 Enterprise Edition to deploy this application. We
discuss other limitations throughout the rest of this chapter.
Defining a Custom Web App
An Access database consists of several objects: tables, queries, forms,
reports, and macros. In Access 2013, you have the option of storing these
database objects locally in an .accdb file or storing them on a SharePoint
2013 server as a Custom Web App. A Custom Web App is a new application
model that allows you to store Access objects on a SharePoint server and
make them available to users without Microsoft Access.
Custom Web Apps allow you to deploy solutions to anyone who has an
Internet connection and a web browser. These apps use SQL Azure or SQL
Server to allow you to share data over the Internet with SharePoint.
If you spent the time to find out about web databases in Access 2010, you
need to rethink the process in Access 2013. Web databases in Access 2010
were Microsoft’s first attempt at moving an Access database to the web. In
Access 2013, Custom Web Apps replace the old functionality and are a huge
leap forward when paired with SharePoint 2013.
Meeting the requirements for a Custom Web App
To create a Custom Web App, you need the following:
Access 2013 (obviously!)
A SharePoint 2013 development environment
Search JabSto ::

Custom Search