| Knowledge Base Article #171 - Getting RTSPrint and BackupMerge to work with PowerBase |
|---|
| Date | Nov 6, 2008 |
| By | ENOSERV |
| Filed Under | PowerBase General |
| Class | General |
| |
| Issue Addressed |
|---|
PowerBase runs an internal RTS database for storing results, library routines, macros, curves, and translation tables.
This internal RTS database can be accessed by RTSPrint and BackupMerge and behaves the same way any other RTS database would. |
| |
| Causes of Issue |
|---|
You can view the Test Results stored in PowerBase and have full access to RTSPrint's result reporting Power
You can backup/merge your library routines in PowerBase so that they get distributed to RTS databases on exports.
You can backup/merge old results from PowerBase into new RTS databases. |
| |
| Solution to this Issue |
|---|
Configuring RTS Print to open the PowerBase Database
1) Open the PBase.ini file, located in your PowerBase directory. Keep this file open for reference
2) Open RTS
3) Select utilities->RTS Options Editor
4) Select the External Programs tab
5) If your PBDatabaseType value in the PBase.ini file is ORACLE
A) Check the �PowerBase for Oracle� box
B) Enter the SERVERNAME value in Pbase.ini in the �oracle server location� box
6) If your PBDatabseType is SYBASE
A) Enter your ASA_DSN name in the �ASA DSN Name� box
B) Enter your ASA_PROVIDER name in the �ASA Provider� box.
7) Launch RTSPrint or BackupMerge either by itself, or through RTS.
8) Hit the Select Database button.
9) In the resulting window, in the Files of Type Dropdown, select �PBase � (Sybase) via ODBC = �ASA� � option for Sybase, or PBase � (Oracle) Native = �Oracle� for Oracle
10) Enter �pb� in the File Name box and hit open.
|