Paint Variables (Using Input FIELD to use in RLIST ?) (AREV Specific)
At 21 NOV 2000 12:34:43PM Philip Hatcher wrote:
Is it possible to use the value from an input field in a Collector
window within the window in a RLIST or Post Process ?
I am trying to capture one or more inputs in a collector window and
then use those values in listing records without having to write a basic program or at least a unique program. I know that there is so many different ways to perform different operations within a window.
I have tried some of the obvious variables i.e @RECORD, @PSEUDO
but these are not usable in a "RLIST" statement. I am trying using the collector window to do some verification or lookup before I list the record(s).
Thanks!
At 21 NOV 2000 12:45PM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
The article at http://www.sprezzatura.com/V4I1A5.HTM seems to do exactly what you want.
World Leaders in all things RevSoft
At 21 NOV 2000 05:41PM Philip Hatcher wrote:
Thank you for the lead ,but I am a little puzzled on if I still need to write a basic program.
I was hoping that I could enter a RLIST statement in a _Customize_ or _Processes_ field in a Collector Window.
I.e. field1=1234 ,field2=01-01-00" …then…
LIST FILE WITH TYPE EQ field1 AND WITH START_DATE GE field2 TYPE START_DATE END_DATE
My hope was to do all of the input and processing in a collector window ?? ( I have only being using "paint" with AREV a couple of months but I have used the 4GL SB+ in "UniVerse", which a little is similar .)
At 21 NOV 2000 05:59PM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
You will need to at least cut a symbolic (I-type).
World Leaders in all things RevSoft
At 21 NOV 2000 07:00PM Bill Titus wrote:
Phillip,
You need to make the following changes to your collector window.
First, place your RList statement in Register 1 of the window during the Paint process. (This is accessed from the Paint menu: Advanced | Registers.)
It should follow this format:
* test for data
IF @RECORD @RECORD) ELSE RETURN
* if there, execute this command
EXECUTE "LIST FILE WITH TYPE EQ ":@RECORD:" AND WITH START_DATE GE :"@RECORD:" TYPE START_DATE END_DATE"
Second, set the Advanced | Collector | Save properties to: Type=1, Code=C, Command=. (You can select a different Save Type to suit your needs.) When the key is pressed, the existence of data is checked. If it does, the RList statement in window register 1 will be executed with the variables from field1 and field2 inserted as you wished.
I assume that you have selected the appropriate field types for each prompt, so the data passed to the RList command will be valid.
Hope it works for you.
Bill
At 21 NOV 2000 07:04PM Bill Titus wrote:
Sure wish I knew how to type…
IF @RECORD @RECORD) ELSE RETURN
should be
IF @RECORD AND @RECORD ELSE RETURN
Sorry for any inconvenience.
Bill
At 22 NOV 2000 10:11AM Philip Hatcher wrote:
Thanks.
I creating a "S" type dict entry reading @PSEUDO then used that
entry in my list statement. The RLIST was placed in -post-processes-
on the window line with a "X" code.
Also, for others, you can chain processes with a ";" separator.
Here is a complete sample:
_Create_
DICT FILENAME
ID : TYPE_ENTER
Type : S
Formula : TYPE_IN=PSEUDO
@ANS=TYPE_IN
_Modify the Collector Window_
Code CommandX;X SELECT FILENAME WITH TYPE EQ TYPE_ENTER;LIST FILENAME TYPE STA_DATE END_DATE
*NOTE* You _MUST_ have the RLIST all on one line!!
At 22 NOV 2000 11:35AM Philip Hatcher wrote:
Thanks Bill.
I appreciate learning more about using the Registers. Also, I like not having to add any DICT entries.
Also, I tried to use the check for "@RECCOUNT" after a "SELECT"
before I did a RLIST but it does not evaluate correctly.
i.e. IF @RECCOUNT ELSE RETURN -or- IF @RECCOUNT GE 1 ELSE RETURN
Any other suggestions, just trying to learn what code can be used where.
At 22 NOV 2000 12:17PM Bill Titus wrote:
Philip,
The EXECUTE command does not pass the results of one process to the next step in a multi-step procedure.
To achieve that result, use PERFORM instead. The code should then work fine.
Have fun!
Bill