Magic User Group

Magic Wiki-Wakka : RecordSuffix

HomePage :: CATEGORIES | Index :: Changes :: Comments :: Search :: Login/Register
Most recent edit on 2012-01-09 21:49:51 by ArchLineberger [corrected spelling]

Additions:
- Delete tasks - if RS operations exists, execute once for each record in Modify mode, then once again in Delete mode

Deletions:
- Delete tasks - if RS operations exist, execute once for each record in Modify mode, then once again in Delete mode



Edited on 2009-04-10 20:07:48 by ArchLineberger [Clarification to "when not executed"]

Additions:
- An undo-able programmatic update occurs within the current task

Deletions:
- An undo-able update occurs within the current task



Edited on 2007-05-08 03:49:03 by ArchLineberger

Additions:
- An undo-able update occurs within the current task

Deletions:
- An update occurs within the current task



Edited on 2007-02-03 17:44:36 by ArchLineberger

Additions:
- An update occurs within the current task

Deletions:
- An update occurs within the current task level



Edited on 2007-02-03 17:41:18 by ArchLineberger

Additions:
- An update occurs within the current task level

Deletions:
- An update occurs at the current task level



Edited on 2007-02-03 17:08:47 by ArchLineberger

Additions:
If one of the following conditions is met, the Record Suffix operations are performed then the database is updated, before the next Record Prefix or the Task Suffix.

First, general rules for when is it not executed:

Now, when it is executed:

Batch Tasks:

Online Tasks:

You would think this an elemetary question. Perhaps it is, but if you cannot always achieve the results you are seeking, look here. There are likely other conditions causing the engine to execute the Record Suffix. If you know of them, please add them to the list:
Batch task
• Executed so long as there is a record in the view.
Online task
• The end-user edited a field, either by an alphanumeric keystroke or
mouseclick on a tab/combobox
• An Update operation with the Undo property set to No occured in the
task or a handler.
• An Input Form operation inserted data in a variable.
• The Force Record Suffix field evaluates to True
• The task mode was changed.
• A subtask (not a handler) CONTAINS an Update operation to a parent variable.
• A subtask varset() CHANGED a variable in the parent.
Categories
CategoryHowTo




Edited on 2006-08-19 23:57:53 by ArchLineberger

Additions:
• A subtask varset() CHANGED a variable in the parent.

Deletions:
• A varset in a child task CHANGED a variable in the parent.



Edited on 2006-08-19 23:54:11 by ArchLineberger

Additions:
• A subtask (not a handler) CONTAINS an Update operation to a parent variable.

Deletions:
• A subtask (not a handler) contains an Update operation to a parent variable.



Oldest known version of this page was edited on 2006-08-19 23:52:35 by ArchLineberger []
Page view:

What causes the record Suffix to execute?


You would think this an elemetary question. Perhaps it is, but if you cannot always achieve the results you are seeking, look here. There are likely other conditions causing the engine to execute the Record Suffix. If you know of them, please add them to the list:

Batch task
• Executed so long as there is a record in the view.

Online task
• The end-user edited a field, either by an alphanumeric keystroke or
mouseclick on a tab/combobox
• An Update operation with the Undo property set to No occured in the
task or a handler.
• A subtask (not a handler) contains an Update operation to a parent variable.
• A varset in a child task CHANGED a variable in the parent.
• An Input Form operation inserted data in a variable.
• The Force Record Suffix field evaluates to True
• The task mode was changed.


Categories
CategoryHowTo
Valid XHTML 1.0 Transitional :: Valid CSS :: Powered by Wikka Wakka Wiki trunk
Page was generated in 0.3008 seconds