I'm sorry that I misspoke. In testing and debugging my conference presentation, trying to figure out if an error was in the R:Tango portion or in the R:Base 7.0 portion, I connected R:Base to a different database, then SCONNECTED to the database with the stored procedure, and did the secret things that should have made the report print. It generated the report file like a charm, and helped me zero in on my spelling error in the R:Tango application file.
Those "secret" tricks will not be secret anymore, after my presentation at the conference in just a little over two weeks! Bill On Tue, 18 Mar 2003 16:54:42 -0500, A. Razzak Memon wrote: >To use that reporting functionality and the ability to use R:BASE >6.5++/7.0 commands via stored procedure, following are the requirements: > >01. R:Tango 5.0 running: > Witango Application Server (Build:058) and higher > Oterro 2.6 (Special version for R:Tango) and higher > R:BASE 6.5++ (Build: 1.865xRT03) and higher > >02. R:BASE 7.0 for Windows (Update 39 and Higher) > Optional: If you would like to display coooool reports designed > in R:BASE 7.0 for Windows via R:Tango 5.0! >
