Message.AddField
Method
Visual Basic
Overloads Public SubAddField
(
ByVal messageField As MessageField)
Overloads Public SubAddField
(
ByVal fieldName As String,
ByVal fieldValue Asvalue_type
)
Overloads Public SubAddField
(
ByVal messageField As MessageField,
ByVal fieldValue Asvalue_type
,
ByVal fieldId As UInt16)
C#
public voidAddField
(MessageField messageField);
public voidAddField
(
string fieldName,
value_type
fieldValue);
public voidAddField
(
string fieldName,
value_type
fieldValue,
ushort fieldId);
Purpose
Overloading
This method has many overloads. Message.add Overloads by Category classifies them into three main categories (based on the number of parameters). Message.add Homologous Types documents the automatic conversion from types in Visual Basic and C# to homologous types within the resulting field in Rendezvous wire format.
Signature |
Description |
messageField
|
The parameter is a message field object, which fully specifies the field—including its name, type, value, and field identifier; see MessageField. |
fieldName, fieldValue
|
Overloads with two parameters add fields without identifiers. The first parameter specifies the name of the new field. Fields without identifiers must have non-null names. The second parameter specifies both the type of the field and its data; see also Message.add Homologous Types. |
fieldName, fieldValue, fieldId
|
Overloads with three parameters add fields with identifiers. The first parameter specifies the name of the new field. A field with an identifier may have a null name. The second parameter specifies both the type of the field and its data; see also Message.add Homologous Types. The third parameter specifies the field identifier. All field identifiers must be unique within each message. Integers in the range [ |
Field Name Length
The the longest possible field name is 127 bytes.
Nested Message
When the fieldValue
argument (that is, the second parameter) is a message object, this method adds only the data portion of the nested message; it does not include any address information or certified delivery information.
Date & Time Representations
Rendezvous software represents time values in two ways—one within programs, and a more compact wire format within messages. In both representations, zero denotes the epoch, 12:00 midnight, January 1st, 1970.
Rendezvous wire format represents time as a two-part value—seconds as a 40-bit signed integer, plus microseconds as a 24-bit unsigned integer. This representation yields the effective range detailed in Date and Time Ranges in Rendezvous Wire Format. Range limits denote the extreme value on either side of zero (the epoch). Bold type indicates the primary unit of measurement.
range in years |
17,432
|
range in seconds |
|
range in milliseconds |
549,755,813,887,000
|