Report Builder and SQL Dataserver

[andrewmtas]

Apologies if this thread is in the wrong forum

We have and existing application with a large number of Report Builder reports. For one client we need to host the application using the Progress SQL dataserver. All our reports run using the aderb\printrb2 methodology. From my reading it should be possible to connect to the SQL DB using this but I have yet to find an explicit statement of the connection syntax to use. The system icon is using a connection string of the following format:

stdholder -H mtasserver -N tcp -S 2907 -db ver7std -dt MSS -ld ver7 -U dbo

where the first connection is the schema holder the second is the SQL db.

I would be grateful of any pointers anyone can give - I have spent a fair amount of time searching Progress KBase and the online Progress forums with no joy so far.

Thanks in advance

 

[vinod_home]

Could you try to connect only the schema holder first and using a program connect to the sql database.

 

[andrewmtas]

Not really an option we have a large number of reports embedded in our system that run a command of the format:

RUN aderb\_prntrb2( ↑
t_Library_Name, /* RB-REPORT-LIBRARY */ ░
REPORT-NAME, /* RB-REPORT-NAME */ ░
t_Connection, /* RB-DB-CONNECTION */ ░
REPORT-INCLUDE-RECORDS, /* RB-INCLUDE-RECORDS */ ░
REPORT-FILTER, /* RB-FILTER */ ░
REPORT-MEMO-FILE, /* RB-MEMO-FILE */ ░
REPORT-PRINT-DESTINATION, /* RB-PRINT-DESTINATION */ ░
REPORT-PRINTER-NAME, /* RB-PRINTER-NAME */ ░
REPORT-PRINTER-PORT, /* RB-PRINTER-PORT */ ░
REPORT-OUTPUT-FILE, /* RB-OUTPUT-FILE */ █
REPORT-NUMBER-COPIES, /* RB-NUMBER-COPIES - zero */ █
REPORT-BEGIN-PAGE, /* RB-BEGIN-PAGE - zero */ █
REPORT-END-PAGE, /* RB-END-PAGE - zero */ █
REPORT-TEST-PATTERN, /* RB-TEST-PATTERN */ █
REPORT-WINDOW-TITLE, /* RB-WINDOW-TITLE */ █
REPORT-DISPLAY-ERRORS, /* RB-DISPLAY-ERRORS */ █
REPORT-DISPLAY-STATUS, /* RB-DISPLAY-STATUS */ █
REPORT-NO-WAIT, /* RB-NO-WAIT */ █
REPORT-PARAMETERS, /* RB-OTHER-PARAMETERS */ █
Report-Temp-File-Destination /* TEMP FILE LOCATION [MOD 2]*/).░

t_connection is then specified as a system wide parameter which we store in the application database via a setup screen. Basically what I need to know is the syntax of t_connection that will connect to the SQL server.