OECGI INET_RLIST Command error in page 2 (OpenInsight 32-bit Specific)
At 30 NOV 2003 12:41:23PM David E Schranz wrote:
I am experiencing a problem when using the Inet_Rlist facility with OECGI.
When running a report :
The first page is displayed correctly but the second and rest of the pages give an error.
Any Suggestions
David Schranz
At 01 DEC 2003 12:54PM Richard Hunt wrote:
David,
You say "when running a report"…
this is sent…
What is submitted when you advance to the next page?
Maybe your OI stored proceedure is not being executed or it is not sending the HTML code for the next page.
At 01 DEC 2003 05:18PM David E Schranz wrote:
http://www.?????/OECGI.exe/INET_RLIST?REPORT_ID=STATS&ARGS=2
is being submitted when I click on the Next Button at the bottom of the 1st report page.
but an OECGI error is received.
At 01 DEC 2003 05:20PM David E Schranz wrote:
When running the report from the 2nd page:
http://www.?????/OECGI.exe/INET_RLIST?REPORT_ID=STATS&ARGS=2
Once I click on the Next Link an
Any Suggestions
David Schranz
At 02 DEC 2003 12:23PM Richard Hunt wrote:
David,
Then verify your "stats" stored proceedure is actually receiving the arguments. And that your "stats" stored proceedure is actually sending the proper "HTML" code back.
Unless I am misunderstanding you… It sounds like your problem is with your "stats" stored proceedure.
At 03 DEC 2003 07:12AM David E Schranz wrote:
The Stats is not a procedure but a Report Builder Report.
The Inet_rlist - Report_ID command actually triggers the report designed in the Report Builder.
This was working well with OICGI but is breaking in OECGI.
TIA
DAvid Schranz
At 03 DEC 2003 08:17AM David E Schranz wrote:
The html code for the 2nd page is:
http://www.?????/cgi-bin/oecgi.exe/INET_RLIST?REPORT_ID=STATS&ARGS=2
This is returning an OECGI error.
At 03 DEC 2003 12:05PM Richard Hunt wrote:
David,
Maybe this will help???
OECGI has no effect on most existing INET_ procedures.
However, if you have INET Procedure that directly interact with the presentation server, for example using Set_Property(), Get_Property(), or Start_Window(), then you will want to find a different technique.
Also, you might want to be sure that any "@" variables you are using are accurate.