form.save

beasscript-logo-small

form.save

 

Save changes from dw_1 and start the update process

this is executed automatically from different processes, but you can activate this with

form.save

too

 

Standard-UPDATE-function

the standard-update functionality is coded to t_update (see the section UPDATE in <%FENSTER-BEARBEITUNG%> ).

 

special commands:

dwupdate        if this is coded then there will be an UPDATE on the Dataform. Sequence order is not important.

 

isnull                if the specified item is NULL there will be a message and the UPDATE sequence is stopped

         Example

         isnull=wkz_id

         if Field is NULL, then beas display: "Error - You must insert a value in this field"

         isnull=wkz_id=msg944$Insert Tool-Id

         if Field is NULL, then beas display: "Error - Insert Tool-Id"

 

primaryfield        primaryfield=wkz_id

         check for uniqueness and null (browser-Edit with more then 1 line)

         if duplicate-key, then beas display: There must be a unique value is required. The value was already entered in line xx

 

default        the specified column gets the specified default value if it is NULL

max                The specified item gets the next higher value:

         max=[item]=[sql-command]

post                the following command is executed AFTER the DWUPDATE but BEFORE quitting the UPDATE-sequence.

         All other commands without POST are executed before the DWUPDATE

 

Sequence of an UPDATE-command:

 

1. all directly specified commands like isnull, default and own commands like if=, goto=, meldung, isnull usw.

2. EVENT UPDATE of the Userobject.of_update()

3. Update of the Dataform when dwupdate is set

4. column "new" is set to N if existing

5. all commands which are specifed with "POST"

 

 

Special behaviour

If the variable sysnoupdate is set to J, there is NO Update and the Update-properties remain active

 

Old: update, edit.end