Collector Window Locking (AREV Specific)
At 20 APR 2000 02:16:44PM David Chan wrote:
I would like to present data in a Collector Window which I would not want any changes made. I am running AREV3.03. Any suggestion re locking? Thanks in advance!
At 20 APR 2000 03:12PM Larry Wilson - TARDIS Systems, Inc. wrote:
You can set wc_locking_on% and wc_wlocked% to null on entry (i.e. pre init) and reset on exit (post window if you are calling the collector from an entry window). You can also set Post window to undo all changes using a local common that was set at pre init.
At 22 APR 2000 03:44AM Curt Putnam wrote:
Since most collectors are populated via @Pseudo, why not just keep a copy of it and don't worry about changes? Or is your worry that folks will waste their time making useless changes?
At 22 APR 2000 11:32AM Don Bakke wrote:
David,
I believe if you just make all the prompts protected but do not skip you will get what you want.
At 25 APR 2000 09:24AM David Chan wrote:
I tried to add subroutine to pre-init but the subroutine crashed with the $insert sysinclude,window_common% with error: Non-Dimensioned Variable used as Array.
If I put the subroutine in pre-read or post-init it won't crash but it won't lock record either.
At 25 APR 2000 09:51AM David Chan wrote:
It's a lot of work (many fields) but it sure works! Thanks!
David
At 29 APR 2000 12:32PM Larry Wilson - TARDIS Systems, Inc. wrote:
To use window_common%, you need to run your collector out of a program by using a catalyst call, and use the $insert of a modified common in the program and then CLEARCOMMON at the top of the program, then when you call the collector you will have access to the common.
This may be as simple as writing a program like:
*** to set up the BP_WINDOW_COMMON%, change the variable wc_w_cnt% to the number of prompts in your collector (change it from a variable to a fixed number); make sure you change it in both places.
$insert sysinclude, bp_window_common%
CLEARCOMMON
call CATALYST('W',collector_name)
Larry
At 30 APR 2000 04:09PM David Chan wrote:
This is very interesting and helpful. I did however, do it the old fashion way - by individually making the prompts "protected" but not "skipped". Thanks for all your help!
David Chan
—————————–7d026ceccc–
At 30 APR 2000 06:31PM Larry Wilson - TARDIS Systems, Inc. wrote:
David,
An interesting extrapolation of calling the collector from a subroutine is that you can set the data and dict variables and thus use symbolics in your collector.