LooperSave (Function)

ONLINE HELP
WINDEV, WEBDEV AND WINDEV MOBILE

Version:

Home | Sign in | English

Help

WLanguage

WLanguage functions

Controls, pages and windows

Updating the data file linked to the Looper control

Cascading input and update of linked data file

Re-displaying the saved row

Locking and updating the data file

Duplicates and referential integrity

Use LooperSave to reduce the number of lines of code

See also

GalleryPopupDisplayed

Looper constants

Looper control management functions

LooperRestorePositionAndSelection

LooperSave

LooperSavePositionAndSelection

LooperSearch

LooperSearchEverywhere

This content has been translated automatically. Click here to view the French version.

Updating the data file linked to the Looper control
Cascading input and update of linked data file
Re-displaying the saved row
Locking and updating the data file
Duplicates and referential integrity
Use LooperSave to reduce the number of lines of code

WINDEV

WEBDEV

WINDEV Mobile

Others

See also

LooperSave (Function)

In french: ZoneRépétéeEnregistre

Validates the modification or addition of the record associated with the current row in the browsing Looper control. The record is updated in the data file linked to the browsing Looper control.

Versions 16 and later

This function is now available for WINDEV applications in Linux.

New in version 16

This function is now available for WINDEV applications in Linux.

Example

// Enregistrement des données du champ Zone répétée "ZR_ZoneProduit"
LooperSave(ZR_ZoneProduit)

Syntax

LooperSave(<Looper control>)

<Looper control>: Control name

Name of Looper control to use. The current row of this Looper control will be recorded in the linked data file.
If this parameter corresponds to an empty string (""), the Looper control to which the current event belongs is used.

Remarks

Updating the data file linked to the Looper control

LooperSave saves the current row of Looper control in the data file linked to the Looper control. The items are automatically assigned with the values of associated controls in the current row.

When a modification is performed, LooperSave replaces the former values by the new ones. The items not found in the Looper control are not modified.

Caution:

LooperSave only supports the data file associated with the Looper control. If some attributes/controls are linked to items found in other data files, these data files are not automatically managed.
The "Image" attributes/controls are not saved by LooperSave. To modify the content of the memo associated with the image (rare case), use HLinkMemo.

Cascading input and update of linked data file

If the cascading input is enabled, the data file linked to the browsing Looper control is automatically modified when the user goes to the next row LooperAdd, LooperAddLine, LooperInsert, LooperInsertLine, LooperModify and LooperModifyLine). LooperSave is useless.

If the cascading input is not enabled, the data file linked to the browsing Looper control is not modified. To write the added row or the modified row into the linked data file, LooperSave must be called after the function used to perform the addition or the modification.

Remarks:

NewLine is used to know whether the current row was just created by LooperAdd, LooperAddLine, LooperInsert and LooperInsertLine (..NewLine = True).
Modified is used to find out whether the current row was modified by direct user input in the Looper control (..Modified = True).

Re-displaying the saved row

After the call to LooperSave, the saved row may "disappear". This "disappearance" is due to the value of the search key for the added or modified record.

To avoid this problem, redisplay the Looper control with LooperDisplay.

Locking and updating the data file

If the data file is locked in the current process, LooperSave saves the current row and unlocks the data file.

Duplicates and referential integrity

If the management of duplicates is enabled (HSetDuplicates), HErrorDuplicates must be checked after the execution of LooperSave to check the key uniqueness.
If the management of referential integrity is enabled (HSetIntegrity), HErrorIntegrity must be checked after the execution of LooperSave to check the referential integrity.

Use LooperSave to reduce the number of lines of code

LooperSave reduces several lines of code. This single line allows you to avoid assigning the item variables one by one.

For example, the following code: is replaced by the following line:

LooperSave(ZR_ZoneRépétéeClient)

Component: wd270obj.dll