Features
Local and remote report processing have different responsibilities:
| Concern | Local ReportViewer / PPJ RDLC path | SSRS server reports |
|---|---|---|
| Processing | In the process hosting the local report engine. | On the report server. |
| Data | The application supplies data; PPJ adapts SAL report input. | The server uses configured report data sources. |
| Definition | RDLC generated for the local adapter. | RDL deployed to the report server. |
| Deployment | Application, report definitions, runtime, and dependencies. | Report server plus deployed definitions, data sources, and access configuration. |
| Scheduling | Requires application-specific implementation. | Server delivery features depend on the product and edition. |
| Export | Formats depend on the installed local engine. | Formats depend on the server's renderers. |
See Microsoft's ReportViewer integration documentation.
PPJ Conversion
Ice Porter generates XML RDLC definitions. PPJ supplies report data at runtime. The distinction is not simply a filename extension: changing .rdlc to .rdl does not supply server data sources, credentials, or a complete server integration.
Validation
Check dataset and field names against the converted definition. Compare expressions, grouping, pagination, fonts, and supported export formats. Test using the deployed runtime: a report that opens in a designer can still depend on an unsupported report-schema version or missing runtime assembly.