Supported Access Report Features (SSRS)
When you import a report into Report Designer, the import process converts the Microsoft Access report into a Reporting Services Report Definition Language (RDL) file. Reporting Services supports several features of Access; however, because of differences between Access and Reporting Services, some items are modified slightly or are not supported. This topic describes how Access report features are converted to RDL.
Some queries contain code that is specific to Access. Access code is not imported with the report. Also, if a query contains embedded strings, the report may not import correctly. To correct this, replace the strings with a character code. For example, replace the comma (,) character with CHAR(34).
The import process does not properly pass the semicolon (;) or XML markup characters (<, >, etc.) in connection string information. If a connection string contains a semicolon or XML markup character, you will have to manually set the password in the new report after the report is imported.
The import process does not import the connection or general timeout settings in the connection string. You may have to adjust these settings after the report is imported.
If you import a report that has a query that contains query parameters, the query will not be converted when the report is imported. To import the query with the report, temporarily replace the query parameters in the Access report with hard-coded values, and then replace them with query parameters after the report is imported.
Reporting Services supports OLE DB data sources, such as SQL Server. If you are importing reports from an Access project (.adp) file, the connection string for the data source is taken from the connection string in the .adp file. If you are importing reports from an Access database (.mdb or .accdb) file, the connection string may point to the Access database and you may have to correct it after the reports are imported. If the data source for the Access report is a query, the query information is stored without modification in the RDL. If the data source for the Access report is a table, the conversion process creates a query based on the table name and the fields in the table.
Reporting Services supports the following Access controls and includes them in converted report definitions.
Note While a SubReport control is converted within the main report, the subreport itself is converted separately.
Reporting Services does not support the following controls:
If Report Designer encounters any of these controls during the import process, a warning is generated and displayed in the Task List window.
Other controls, like ActiveX and Office Web Components, are not imported. For example, if an Access report contains an OWC Chart control, it will not be converted when the report is imported.
Reporting Services supports the following properties, which are available through the Access user interface. Properties available only in code are not supported and are not listed here.
Reporting Services does not support the following properties, which are available through the Access user interface.
Access defines a group level using a combination of three properties: the group expression, the GroupOn property, and the GroupInterval property. A group that does not have a group header or footer is merged with the group contained within it. If the group does not contain another group, sorting is applied to the detail section and the group is dropped.
Access uses expressions to specify values that appear in text boxes. Access uses Visual Basic as its expression language in addition to some aggregate functions. Report Designer converts these Access expressions to report expressions.
A Reporting Services report definition uses Visual Basic .NET as its native expression language, while Access 2002 uses Visual Basic. The following lists describe the functions that are supported by Reporting Services.
Reporting Services supports the following array functions:
Reporting Services supports the following conversion functions.
Reporting Services does not support the following conversion functions:
Reporting Services supports the following database functions.
Reporting Services does not support the following database functions.
Reporting Services supports the following date/time functions.
Reporting Services does not support the following DDE/OLE functions.
Domain Aggregate Functions
Reporting Services does not support the following domain aggregate functions.
Error Handling Functions
Reporting Services supports the following error handling functions.
Reporting Services does not support the following error handling function:
Reporting Services supports the following financial functions.
Reporting Services supports the following interaction functions.
Reporting Services does not support the following interaction functions.
Reporting Services supports the following inspection functions.
Reporting Services does not support the following inspection function:
Reporting Services supports the following math functions.
Reporting Services does not support the following message functions.
Program Flow Functions
Reporting Services supports the following program flow functions.
SQL Aggregate Functions
Reporting Services supports the following SQL aggregate functions.
Reporting Services supports the following text functions.
Access does not support special Visual Basic constants (for example, vbTrue) in expressions, so no conversion is necessary. However, there is one exception: the keyword Null is converted to System.DbNull.Value.
During the import process, Report Designer scans each expression within a report for variables that do not correspond to field names or controls. These variables are added to report parameters.
The data type for stored procedure parameters is always imported as string. After the report is imported, you must manually change the parameter to use the correct data type.
Access allows fields to have the same name as controls; Reporting Services does not. Visual Basic 6.0 allows spaces in variable names; Visual Basic .NET does not. The import process replaces the names of all such objects with valid names and assigns unique names if more than one object has the same name. Each expression is scanned and the names of variables that correspond to renamed objects are replaced with the new names.
All bitmaps that are embedded within a report are converted to .bmp format when the report is imported, regardless of their initial format. For example, if your report includes .jpg and .gif files, the resulting resources imported with the report are .bmp files. The bitmaps are stored as embedded images in the report. For information about Embedded Images, see Images (Report Builder 3.0 and SSRS).