Part V: Access and Windows SharePoint Services
1176
Control issues
Form and report headers and footers cannot contain bound controls. You have to move bound
controls to the body of the form or report or replace bound controls with unbound equivalents.
Unsupported report controls
The list of unsupported report controls is surprisingly long. This is probably because Access
Services reports are expressed as SSRS (SQL Server Reporting Services) reports and are therefore
limited to the set of controls supported by SSRS. The unsupported controls are ActiveX Controls,
Attachment, Bound Object Frame, Button, Chart, ComboBox, Insert Page Break, Remove Page
Break, Insert Page, ListBox, Option, Option Group, Rectangle, Subform, Subreport, Toggle Button,
and Unbound Object Frame.
The supported controls on Access Services reports are CheckBox, Detail, Empty Cell, Group
Footer, Group Header, Hyperlink, Image, Label, Page Footer, Page Header, Report, Report Footer,
Report Header, and TextBox.
Reports do not support events
All event procedures must be removed from reports. SSRS reports do not support events.
Reports do not support subreports
Subreport controls must be removed from reports.
Object name violations
SharePoint has a problem with object names that contain punctuation. If any of your forms,
reports, or controls include the following punctuation characters, they must be removed before
publishing:
/ \ : *? ““ < > | # <TAB> { } % ~ &
Query errors
Some queries are incompatible with Access Services. For instance, you may have to reconstruct
some queries to remove references to custom VBA functions, or to simplify queries that use sub-
queries. In particular, Access Services has a hard time dealing with queries that reference same-
named fields in multiple tables, so you may have to rename fields in your tables to accommodate
this issue.
Problems with SQL statements
Access Services can’t evaluate SQL statements in queries for many reasons. The SQL statement
may, for instance, reference a Web-incompatible object. If Access Services can’t evaluate the object,
the SQL statement is invalid. The best way to resolve SQL issues is to review the SQL statement in
Access Query Designer. Very often, the issue becomes obvious because Query Designer fails to dis-
play the query’s details in the QBE grid.
