RPC HELP Mult Assign: Difference between revisions
From VistApedia
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[RPC_Broker_Help| RPC Broker Help Home]] | [[RPC_Broker_Help| RPC Broker Help Home]] | ||
<H2>Assign Method (TMult Class)</h2> | <H2>Assign Method (TMult Class)</h2> | ||
Example | [[RPC_HELP_Mult_Assign|Back]] | ||
[[RPC_HELP_TMult_Assign_Example|Example]] | |||
<h3>Applies to</h3> | <h3>Applies to</h3> | ||
[[RPC_HELP_TMult|TMult]] class | [[RPC_HELP_TMult|TMult]] class | ||
<h3>Declaration</h3> | <h3>Declaration</h3> | ||
procedure Assign(Source: TPersistent); | procedure Assign(Source: TPersistent); | ||
Revision as of 23:45, 3 July 2015
Assign Method (TMult Class)
Applies to
TMult class
Declaration
procedure Assign(Source: TPersistent);
Description
The Assign method for a TMult class takes either a Tstrings, a TStringList, or another TMult. In the case where the source is a TMult, the owner of the Assign method gets the exact copy of the source with all string subscripts and values. In the case where the source is a Tstrings or a TStringList, the items are copied such that the strings property of each item becomes the Value, while the index becomes the subscript in the string form.
NOTE: See RPC Limits for information about the size of parameters and results that can be passed to and returned from the TMult class.
