4.2 SQL Server Schemas
Within the dedicated SQL Server
database, Access leverages three separate SQL Server schemas: Access,
AccessSystem, and AccessRuntime. The AccessSystemAccessRuntime
schemas store the system information used by Access Services and the
ADS to allow the web app to function properly. These schemas are used
both by the Access web app at run time and the Access client during
design-time activities. and
The Access
schema contains all the application’s end user-created tables, queries,
and macros. This is where advanced users connect SQL Server reporting
services or other external self-service BI applications for advanced
integration and extension scenarios.
As mentioned previously, SQL Server login details
are available in the application’s Backstage Info section. In addition
to the server and database details, the Manage connections button
enables the creation of new logins with read or read/write permissions.
This enables explicit control of who can access back-end data without
requiring advanced knowledge of SQL Server permissions management
techniques.
4.3 Applications: Views and Reports
In an Access web application, a view is
the main interactive page for browsing users to use the app. The Access
2013 client app refers to these same constructs as forms.
Views in an Access 2013 application are automatically generated to
accelerate the developer through the UI layout tasks and to ensure a
level of consistency across interfaces. Each view is available for
customization inside of the Access design surface. Like tables and
queries, views are stored in the SQL Server database. However, because
they are HTML and JavaScript rather than native SQL objects, such as
tables or table-value functions, views are stored as text in the Access
system tables.
Access web apps offer four distinct types of views for data-centric business application developers:
- List Details — A single scrolling
column of records with an editable details interface for each record on
the right of the records list. The list of records is searchable and
filterable.
- Datasheet — An editable Excel-like grid. Each column in the datasheet grid is sortable and filterable.
- Summary — A view used to group records.
- Blank — Entirely customizable views capable of hosting any of the twelve available Access controls.
A view must be based on a table. The act of
creating a new table automatically generates the List Details and
Datasheet views. The views are organized by the tables they’re
associated with. The views for each table can be moved. In addition,
views can be edited, duplicated, renamed, and deleted.
4.4 Customizing Views
Access 2013 shipped with a built-in
design surface, but the designer for web apps is less precise than the
designer for desktop database applications. The view designer and the
12 controls available to Access developers are intended to keep web
applications designed by business-savvy Access developers from
requiring web design skills.
The view designer works on a grid system that
automatically ensures components line up and are spaced properly. After
a control has been added to a view, selecting the control allows access
to the relevant properties in a pop-up, as shown in Figure 3.
Note that the available properties are divided into Data, Formatting,
and Actions categories, and each is accessed by distinct buttons in the
view designer.
Also visible in Figure 3
is the Action Bar, which contains icons for actions such as New,
Delete, Edit, Save, and Cancel. The green plus sign allows the addition
of custom actions. Access offers web app developers 20 different custom
actions to choose from. These actions will be explored in the
“Applications: Macros section.” In addition to the ability to add
custom actions, web app developers can opt to delete buttons or even
hide the Action Bar as the business process dictates.
4.5 Applications: Macros
Where previous versions of Access
leverage VBA to add automation and business logic to an application,
Access 2013 web apps rely on data macros. Users familiar with
SharePoint Designer’s If-Then-Else workflow designer will be at home
with Access 2013’s data macro designer, as shown in Figure 4.
Macros come in three main varieties, as described by the Access 2013 user interface:
- Data macros
- User Interface macros
- On-Start macros
