Kbase 20557: Deploying Report Builder Reports
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/3/2005 |
|
Status: Unverified
GOAL:
How to deploy a Progress Report Builder report?
GOAL:
Deploying Report Builder Reports
FIX:
The first question to address is whether the end users of the report need to edit the reports themselves. If they do, the report users must have access to Report Builder itself. If not, Progress recommends using the RBengine. This solution does not take into account licensing issues.
Things to keep in mind when deploying with Report Builder:
- End users must understand how to use Report Builder.
- Connection parameters to the database are embedded into each report.
- If the user environments are configured differently (for example, a difference in the database connection parameters to the database or databases upon the first opening of a report) Report Builder must be directed to the database and then save the report.
There is no automated process for this.
Things to keep in mind when deploying with Report Builder Engine:
- Make sure it is possible to spawn the report from within a 4GL application.
- Users can preview and print reports but cannot edit them.
- Filters and queries can be performed in the 4GL and then passed through the report format and design.
- The RB/DB connection can be stored locally in a variable to be passed through the RB/DB connection parameters, thus allowing the override of the saved database connection information for a report.