Syntax
| Visual Basic (Declaration) | |
|---|---|
Public Function New() | |
| Visual Basic (Usage) |  Copy Code |
|---|---|
Dim instance As New GetBulkMessage() | |
| C# | |
|---|---|
public GetBulkMessage() | |
| Managed Extensions for C++ | |
|---|---|
public: GetBulkMessage(); | |
| C++/CLI | |
|---|---|
public: GetBulkMessage(); | |
Remarks
The application must set NonRepeaters and Repetitions, and then add the corresponding "non-repeating" Variable instances followed by the "repeating" Variable instances. The "non-repeating" variables behave like a GetNextMessage, so the first GetBulkMessage.NonRepeaters will be returned as that many variables in the ResponseMessage. The "repeating" variables behave like GetNextMessage, so up to that many variable objects will be returned in the ResponseMessage for each "repeating" variable added to the list.
The application will typically set GetBulkMessage.NonRepeaters to 0 and GetBulkMessage.Repetitions to the maximum number of rows expected in the table of interest. Then variables are added to MessageBase.Variables that represent the OID for each table column in the table. When the returned MessageBase.Variables collection is enumerated, each IID should be parsed to determine which value belongs to each row in each table column. The IID for each value is the OID of the table column to which it belongs with the "indexer" into that row added as a suffix. Repeating variables are returned as consecutive rows. For example, if 5 column "repeaters" are provided as OID variables, then the first row is returned in the first 5 variables of the response, the second row is returned in the second 5 variables, and so on.
Requirements
Target Platforms: Microsoft .NET Framework 2.0