[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]


==== View data question (OpenInsight Specific) ====
=== At 26 JAN 2001 04:30:41PM b cameron wrote: ===
 
{{tag>"OpenInsight Specific"}}
 
<QUOTE>
I've used OR_View in a number of apps.



I was wondering if it was possible to get the results that or_view

displays so I can display in my own form editbox?

This way I wouldn't have to recreate the wheel.  

Is this clear as mud?


</QUOTE>
----

=== At 27 JAN 2001 02:35PM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url]  wrote:  ===

<QUOTE>Well essentially as far as we are able to tell OR_VIEW just uses the callback functionality of RLIST to populate a window so could you not just use this?



[url=http://www.sprezzatura.com" ]The Sprezzatura Group[/url] 

[i]World Leaders in all things RevSoft[/i] 

[img]http://www.sprezzatura.com/zz.gif[/img] 

 

 

</QUOTE>

----

=== At 28 JAN 2001 04:01PM b cameron wrote:  ===

<QUOTE>I'm not sure I follow you.  

So, doing the call to RLIST would return the 

results to where so I could put them in an

edit box?



Thanks.

</QUOTE>

----

=== At 29 JAN 2001 04:57AM Oystein Reigem wrote:  ===

<QUOTE>Bruce,



It's not properly docced. I don't remember if it's been described on the discussion lists.



Anyway - here's something I got to work with a little bit of trial and error:



function Test_Rlist_Callback( Arg )

	$insert Rlist_Equates

	declare subroutine Rlist

	CallbackFunc=TEST_CALLBACK"

	/* insert your favourite OpenList LIST statement here */

	RlistScript=LIST TOPO JUSTLEN 4 TOPONAVN JUSTLEN 20 BY TOPONAVN WITH TOPONAVN ] 'A'"

	UserArg="

	RList( RlistScript, TARGET_CALLBACK$, CallbackFunc, UserArg, 0 )

	if Get_Status() then

		debug

	end

return 0



function Test_Callback( Arg1, Arg2, Arg3 )

	/* admittedly this callback function of mine doesn't do much,

	   but the debug statement gives you an opportunity

	   to inspect the arguments.

	   i think the first one tells you what kind the

	   current line is - header, normal text, or whatever.

	   the second contains the line itself - note the tabs.

	   the third was null in my experiments,

	   but seemed to be necessary */

	debug

/* your callback function must return true$ - if everything is ok.

   return false$ if you want to abort the process */

return 1



If you want to run a predefined report you can use the UserArg parameter instead of RlistScript. Something like this (according to the Inet_Rlist function source):

	userArg ="

	userArg=ReportName

	userArg=ReportArgs



Good luck!



- Oystein -



</QUOTE>

----

=== At 29 JAN 2001 12:02PM b cameron wrote:  ===

<QUOTE>Oy,



You da man!



Thanks.

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=840AD21666BCCB8D852569E000762A7E|View this thread on the  forum...]]