[[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]]
==== AMV Behavior ( CTLR+D) (AREV Specific) ====
=== At 20 FEB 2003 03:04:56PM Dave Berkovsky wrote: ===
{{tag>"AREV Specific"}}
I am trying to fugure out how to call a subroutine when user presses
ctrl+d to delete AMV. Any thoughts?
TIA
Dave Berkovsky
----
=== At 20 FEB 2003 03:15PM Donald Bakke wrote: ===
Dave,
You capture this using the Post Prompt process of the AMV field(s). You can determine if the Ctrl-D was pressed by seeing what WC_AMV_ACTION% is equal to at the time. I.e.:
$insert SysInclude, WINDOW_COMMON%
$insert SysInclude, WINDOW.CONSTANTS
Action=WC_AMV_ACTION%
Begin Case
....Case Action EQ AMV.INSERT$
......../* CTRL-N was pressed */
....Case Action EQ AMV.DELETE$
......../* CTRL-D was pressed */
End Case
dbakke@srpcs.com
[url=http://www.srpcs.com]SRP Computer Solutions, Inc.[/url]
[img]http://www.srpcs.com/srpicon1.gif[/img]
----
=== At 21 FEB 2003 08:23AM Dave Berkovsky wrote: ===
Thanks Donald. That worked, but unfortunately @RECORD is not update
at that time. AMV field that was being deleted is still part of
@RECORD. Is there anything else I can do?
----
=== At 21 FEB 2003 08:25AM Dave Berkovsky wrote: ===
Thanks Donald. That worked, but unfortunately @RECORD is not update
at that time. AMV field that was being deleted is still part of
@RECORD. Is there anything else I can do?
----
=== At 21 FEB 2003 09:37AM Don Miller - C3 Inc. wrote: ===
You can check @RECORD in a Post-Prompt or Pre-Save subroutine. I do this frequently during testing:
SUBROUTINE TEST
* insert the common block variables if you want to debug them
DEBUG
* when the debugger is active, you can inspect All variables here to check for what's happening
RETURN
You can place a call to this routine anywhere you want .. Pre-Prompt, Post-Prompt, Pre-Save, etc.
HTH
Don M.
----
=== At 22 FEB 2003 12:15PM Rod Morris wrote: ===
I have had success with this using a perpetual process that tests for what type of AMV.ACTION has happened then performing the appropriate subroutine.
[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=2D3553FEF30DFCB485256CD3006E50F9|View this thread on the forum...]]