|
|
|
|
|
- Use conditions
- Updating the data file linked to the Table or TreeView Table control
- Cascading input and update of linked data file
- Re-displaying the row that was saved
- Locking and updating the data file
- Duplicates and referential integrity
- Use <Table>.Save to reduce the number of lines of code
<Table>.Save (Function) In french: <Table>.Enregistre Updates or adds the record bound to the current row in the Table or TreeView Table control. The record is updated: - in the data file linked to the control.
- in the variable bound to the control.
// Save the data found on the current row // for the "TABLE_Product" control TABLE_Product.Save()
// Save the data found on row 5 // while modifying a column through programming TABLE_Product = 5 TABLE_Product[5].COL_Cap = "new value" TABLE_Product.Save()
// Event Row exit IF TABLE_Customer.Modified = False THEN RETURN END pclFormPresentation is PCustomerForm dynamic IF TABLE_Customer.NewLine THEN pclFormPresentation<-gclPresentation.New() ELSE pclFormPresentation<-gclPresentation.Modify() END TABLE_Customer.Save(pclFormPresentation)
Syntax <Table control>: Control name Name of the Table control based on a data file to be used. Use conditions <Table>.Save can be used on: - a Table control based on a data file or a TreeView Table control based on a data file.
- a single-selection or multi-selection control. For a multi-selection control, only the last selected record is modified (the record corresponding to the last current row).
- a Table control on variable (syntax 2).
Updating the data file linked to the Table or TreeView Table control <Table>.Save saves the current control row in the data file linked to the control. The items are automatically assigned with the values of associated columns in the current row. When a modification is performed, <Table>.Save replaces the former values by the new ones. The items not found in the control are not modified. Caution: - <Table>.Save only manages the data file associated with the control. If some columns are linked to items found in other data files, these data files are not automatically managed.
- The "image" columns are not saved by <Table>.Save. To modify the content of the memo associated with the image (rare case), use <Source>.LinkMemo.
- In the Check Box columns, the call to <Table>.Save is implicit and it cannot be disabled. In any case, the modification of the value of check box will be applied to the data file.
Cascading input and update of linked data file - If the cascading input is enabled, the data file linked to the Table or TreeView Table control is automatically modified when the user goes to the next row (use of <Table>.Add, <Table>.AddLine, <Table>.Insert, <Table>.InsertLine, <Table>.Modify and <Table>.ModifyLine). <Table>.Save is useless.
- If the cascading input is not enabled, the data file linked to the Table or TreeView Table control is not modified. To write the added or modified row into the linked data file, <Table>.Save must be used after the addition or modification function.
Remarks: Re-displaying the row that was saved After the call to <Table>.Save, the row saved may "disappear". This "disappearance" is due to the value of the search key for the added or modified record. To avoid this problem, re-display the Table or TreeView Table control with <Table>.Display. Locking and updating the data file If the data file is locked in the current process, <Table>.Save saves the current row and unlocks the data file. Duplicates and referential integrity Use <Table>.Save to reduce the number of lines of code <Table>.Save reduces several lines of code. This single line allows you to avoid assigning the item variables one by one. For example, the following code: Customer.LastName = LastNameColumn Customer.FirstName = FirstNameColumn Customer.Address = AddressColumn Customer.ZC = ZCColumn Customer.City = CityColumn HAdd(Customer) is replaced with the following line:
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|