# PipeClient Control

The PipeClient control is a simple client for connecting and communicating over named pipes.

## Syntax

**PipeClient**

## Remarks

The PipeClient control is used to connect to an existing pipe server. After connecting the transfer of data is handled very similarly to socket communication.

To begin, first set [PipeName](#pipename-property-pipeclient-control) to the name of the pipe to which the connection will be made. Call [Connect](#connect-method-pipeclient-control) or set [Connected](#connected-event-pipeclient-control) to True to establish the connection. The [Connected](#connected-event-pipeclient-control) event will fire when the connection is complete.

After connecting call [Send](#send-method-pipeclient-control) or [SendFile](#sendfile-method-pipeclient-control) to send data. Incoming data is received through the [DataIn](#datain-event-pipeclient-control) event.

To disconnect call [Disconnect](#disconnect-method-pipeclient-control) or set [Connected](#connected-property-pipeclient-control) to False.

**Synchronous and Asynchronous Operation**

If the [Timeout](#timeout-property-pipeclient-control) property is set to 0, the control will behave asynchronously and all operations return immediately, potentially failing with an error if they can't be completed immediately.

If [Timeout](#timeout-property-pipeclient-control) is set to a positive value, the control will behave synchronously and wait for the operation to complete before returning control.

The control will use [DoEvents](#doevents-method-pipeclient-control) to enter an efficient wait loop during any potential waiting period, making sure that all system events are processed immediately as they arrive. This ensures that the host application does not freeze and remains responsive.

If [Timeout](#timeout-property-pipeclient-control) expires, and the operation is not yet complete, the control fails with an error.

NOTE: By default, all timeouts are *inactivity timeouts*, that is, the timeout period is extended by [Timeout](#timeout-property-pipeclient-control) seconds when any amount of data is successfully sent or received.

The default value for the [Timeout](#timeout-property-pipeclient-control) property is 60 seconds.

##  Property List

*The following is the full list of the properties of the control with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [AcceptData](#acceptdata-property-pipeclient-control) | This property indicates whether data reception is currently enabled. |
| [BytesSent](#bytessent-property-pipeclient-control) | This property includes the number of bytes actually sent after a call to the SendBytes method. |
| [Connected](#connected-property-pipeclient-control) | Triggers a connection or disconnection. |
| [EOL](#eol-property-pipeclient-control) | This property is used to break the incoming data stream into chunks separated by EOL . |
| [PipeName](#pipename-property-pipeclient-control) | The name of the pipe. |
| [RecordLength](#recordlength-property-pipeclient-control) | The length of received data records. |
| [SingleLineMode](#singlelinemode-property-pipeclient-control) | This property includes a special mode for line-oriented protocols. |
| [Timeout](#timeout-property-pipeclient-control) | This property includes the timeout for the control. |

## Method List

*The following is the full list of the methods of the control with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [Config](#config-method-pipeclient-control) | Sets or retrieves a configuration setting. |
| [Connect](#connect-method-pipeclient-control) | Connects to a named pipe. |
| [Disconnect](#disconnect-method-pipeclient-control) | Disconnects from the named pipe. |
| [DoEvents](#doevents-method-pipeclient-control) | This method processes events from the internal message queue. |
| [GetLine](#getline-method-pipeclient-control) | This method gets a line of text from the server. |
| [Interrupt](#interrupt-method-pipeclient-control) | This method interrupts the current action. |
| [ProcessData](#processdata-method-pipeclient-control) | This method reenables data reception after a call to PauseData . |
| [Send](#send-method-pipeclient-control) | Sends data over the connected pipe. |
| [SendBytes](#sendbytes-method-pipeclient-control) | This method sends binary data over the connected pipe. |
| [SendFile](#sendfile-method-pipeclient-control) | Sends the file over the connected pipe. |
| [SendLine](#sendline-method-pipeclient-control) | This method sends a string followed by a newline. |
| [SendText](#sendtext-method-pipeclient-control) | This method sends text over the connected pipe. |

## Event List

*The following is the full list of the events fired by the control with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [Connected](#connected-event-pipeclient-control) | Fired immediately after a connection completes. |
| [DataIn](#datain-event-pipeclient-control) | This event is fired when data (complete lines) come in. |
| [Disconnected](#disconnected-event-pipeclient-control) | Fired when a connection is closed. |
| [Error](#error-event-pipeclient-control) | Fired when information is available about errors during data delivery. |
| [ReadyToSend](#readytosend-event-pipeclient-control) | Fired when the control is ready to send data. |

## Config Settings

*The following is a list of config settings for the control with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [AbsoluteTimeout](#AbsoluteTimeout) | Determines whether timeouts are inactivity timeouts or absolute timeouts. |
| [InBufferSize](#InBufferSize) | The size in bytes of the output buffer. |
| [MaxLineLength](#MaxLineLength) | The maximum amount of data to accumulate when no EOL is found. |
| [OutBufferSize](#OutBufferSize) | The size in bytes of the input buffer. |
| [PipeDirection](#PipeDirection) | Determines the direction data flows. |
| [CodePage](#CodePage) | The system code page used for Unicode to Multibyte translations. |
| [MaskSensitiveData](#MaskSensitiveData) | Whether sensitive data is masked in log messages. |
| [UseInternalSecurityAPI](#UseInternalSecurityAPI) | Whether or not to use the system security libraries or an internal implementation. |

# AcceptData Property ([PipeClient](#pipeclient-control) Control)

This property indicates whether data reception is currently enabled.

## Syntax

```text
pipeclientcontrol.AcceptData
```

## Default Value

True

## Remarks

This property indicates whether data reception is currently enabled. When *False*, data reception is disabled and the [DataIn](#datain-event-pipeclient-control) event will not fire. Use the PauseData and [ProcessData](#processdata-method-pipeclient-control) methods to pause and resume data reception.

This property is read-only and not available at design time.

## Data Type

Boolean

# BytesSent Property ([PipeClient](#pipeclient-control) Control)

This property includes the number of bytes actually sent after a call to the SendBytes method.

## Syntax

```text
pipeclientcontrol.BytesSent
```

## Default Value

0

## Remarks

This property indicates how many bytes were sent after the last call to [SendBytes](#sendbytes-method-pipeclient-control). Please check the [SendBytes](#sendbytes-method-pipeclient-control) method for more information.

NOTE: that BytesSent will always return 0 when the control is operating in synchronous mode (i.e., the [Timeout](#timeout-property-pipeclient-control) property is set to a positive value.)

This property is read-only and not available at design time.

## Data Type

Integer

# Connected Property ([PipeClient](#pipeclient-control) Control)

Triggers a connection or disconnection.

## Syntax

```text
pipeclientcontrol.Connected
```

## Default Value

False

## Remarks

This property indicates whether the control is connected to the remote host. Use the [Connect](#connect-method-pipeclient-control) and [Disconnect](#disconnect-method-pipeclient-control) methods to manage the connection.

This property triggers a connection or disconnection. Setting this property to True makes the control attempt to connect to the pipe identified by the [PipeName](#pipename-property-pipeclient-control) property. If successful, after the connection is achieved the value of the property changes to True and the [Connected](#connected-event-pipeclient-control) event is fired.

Setting this property to False closes the connection.

This property is read-only and not available at design time.

## Data Type

Boolean

# EOL Property ([PipeClient](#pipeclient-control) Control)

This property is used to break the incoming data stream into chunks separated by EOL .

## Syntax

```text
pipeclientcontrol.EOL[=string]
```

## Default Value

""

## Remarks

This property is used to define boundaries in the input stream using the value of the property.

This property is especially useful with ASCII files. Setting it to CRLF (*Chr$(13) & Chr$(10)*) enables the incoming ASCII text stream to split into defined lines. In this case, one event is fired for each line received (as well as in packet boundaries). The CRLF (*Chr$(13) & Chr$(10)*) bytes are discarded.

This property is a binary string. Notably, this means that it can be more than one byte long, and it can contain NULL bytes.

To read or write binary data to the property, a Variant (Byte Array) version is provided in **.EOLB**.

## Data Type

Binary String

# PipeName Property ([PipeClient](#pipeclient-control) Control)

The name of the pipe.

## Syntax

```text
pipeclientcontrol.PipeName[=string]
```

## Default Value

""

## Remarks

This property specifies the name of the pipe.

This may be the name by itself, for instance "MyPipe", or in the format "\\.\pipe\MyPipe".

## Data Type

String

# RecordLength Property ([PipeClient](#pipeclient-control) Control)

The length of received data records.

## Syntax

```text
pipeclientcontrol.RecordLength[=integer]
```

## Default Value

0

## Remarks

If set to a positive value, this property defines the length of data records to be received. The control will accumulate data until RecordLength is reached and only then fire the [DataIn](#datain-event-pipeclient-control) event with data of length RecordLength. This allows data to be received as records of known length. This value can be changed at any time, including within the [DataIn](#datain-event-pipeclient-control) event.

The default value is 0, meaning this property is not used.

This property is not available at design time.

## Data Type

Integer

# SingleLineMode Property ([PipeClient](#pipeclient-control) Control)

This property includes a special mode for line-oriented protocols.

## Syntax

```text
pipeclientcontrol.SingleLineMode[=boolean]
```

## Default Value

False

## Remarks

When this property is set to True, the control treats the incoming data stream as lines separated by carriage return line feed (CRLF), CR, or LF. The [EOL](#eol-property-pipeclient-control) property is ignored.

When this property is set to True, [AcceptData](#acceptdata-property-pipeclient-control) automatically will be set to False. Please refer to the [GetLine](#getline-method-pipeclient-control) method for more information.

This property is not available at design time.

## Data Type

Boolean

# Timeout Property ([PipeClient](#pipeclient-control) Control)

This property includes the timeout for the control.

## Syntax

```text
pipeclientcontrol.Timeout[=integer]
```

## Default Value

60

## Remarks

If the Timeout property is set to 0, all operations return immediately, potentially failing with a *WOULDBLOCK* error if data cannot be sent immediately.

If Timeout is set to a positive value, data is sent in a blocking manner and the control will wait for the operation to complete before returning control. The control will handle any potential *WOULDBLOCK* errors internally and automatically retry the operation for a maximum of Timeout seconds.

The control will use [DoEvents](#doevents-method-pipeclient-control) to enter an efficient wait loop during any potential waiting period, making sure that all system events are processed immediately as they arrive. This ensures that the host application does not freeze and remains responsive.

If Timeout expires, and the operation is not yet complete, the control fails with an error.

NOTE: By default, all timeouts are *inactivity timeouts*, that is, the timeout period is extended by Timeout seconds when any amount of data is successfully sent or received.

The default value for the Timeout property is 60 seconds.

## Data Type

Integer

# Config Method ([PipeClient](#pipeclient-control) Control)

Sets or retrieves a configuration setting.

## Syntax

```text
pipeclientcontrol.Config ConfigurationString
```

## Remarks

Config is a generic method available in every control. It is used to set and retrieve [configuration settings](#config-settings-pipeclient-control) for the control.

These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the control, access to these *internal properties* is provided through the Config method.

To set a configuration setting named *PROPERTY*, you must call *Config("PROPERTY=VALUE")*, where *VALUE* is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).

To read (query) the value of a [configuration setting](#config-settings-pipeclient-control), you must call *Config("PROPERTY")*. The value will be returned as a string.

# Connect Method ([PipeClient](#pipeclient-control) Control)

Connects to a named pipe.

## Syntax

```text
pipeclientcontrol.Connect
```

## Remarks

This method connects to a named pipe specified by [PipeName](#pipename-property-pipeclient-control). Calling this method is equivalent to setting the [Connected](#connected-property-pipeclient-control) property to True.

**Example (Connecting)**

```text
PipeClient.PipeName = "MyPipe";
PipeClient.Connect();
```

# Disconnect Method ([PipeClient](#pipeclient-control) Control)

Disconnects from the named pipe.

## Syntax

```text
pipeclientcontrol.Disconnect
```

## Remarks

This method disconnects from the pipe. Calling this method is equivalent to setting the [Connected](#connected-property-pipeclient-control) property to False.

# DoEvents Method ([PipeClient](#pipeclient-control) Control)

This method processes events from the internal message queue.

## Syntax

```text
pipeclientcontrol.DoEvents
```

## Remarks

When DoEvents is called, the control processes any available events. If no events are available, it waits for a preset period of time, and then returns.

# GetLine Method ([PipeClient](#pipeclient-control) Control)

This method gets a line of text from the server.

## Syntax

```text
pipeclientcontrol.GetLine
```

## Remarks

This method gets a line of text from the server. This method is an alternative method of receiving data for line-oriented protocols. The control will block if necessary and then will return the received line. [AcceptData](#acceptdata-property-pipeclient-control) will be set automatically to True when the method is called, and then will be set to False after a line is received.

Please refer to the [SingleLineMode](#singlelinemode-property-pipeclient-control) property for more information.

# Interrupt Method ([PipeClient](#pipeclient-control) Control)

This method interrupts the current action.

## Syntax

```text
pipeclientcontrol.Interrupt
```

## Remarks

This method interrupts the current action. If you use [SendFile](#sendfile-method-pipeclient-control) to upload a file, the control will run synchronously until the upload is completed. This method will allow you to stop the file from uploading without disconnecting from the host.

# ProcessData Method ([PipeClient](#pipeclient-control) Control)

This method reenables data reception after a call to PauseData .

## Syntax

```text
pipeclientcontrol.ProcessData
```

## Remarks

This method reenables data reception after a previous call to PauseData. When PauseData is called, the [DataIn](#datain-event-pipeclient-control) event will not fire. To reenable data reception and allow [DataIn](#datain-event-pipeclient-control) to fire, call this method.

NOTE: This method is used only after previously calling PauseData. It does not need to be called to process incoming data by default.

# Send Method ([PipeClient](#pipeclient-control) Control)

Sends data over the connected pipe.

## Syntax

```text
pipeclientcontrol.Send Text
```

## Remarks

This method sends data to the server.

# SendBytes Method ([PipeClient](#pipeclient-control) Control)

This method sends binary data over the connected pipe.

## Syntax

```text
pipeclientcontrol.SendBytes Data
```

## Remarks

This method sends the specified binary data to the server. To send text, use the [SendText](#sendtext-method-pipeclient-control) method instead.

When [Timeout](#timeout-property-pipeclient-control) is set to 0 the control will behave asynchronously. If you are sending data to the receiving process faster than it can process it, the outgoing queue might fill up. When this happens, the control fails with error 25036: "[10035] Operation would block" (WSAEWOULDBLOCK). You can trap this error, and then try to send the data again. The [BytesSent](#bytessent-property-pipeclient-control) property shows how many bytes were sent (if any). If 0 bytes were sent, then you can wait for the [ReadyToSend](#readytosend-event-pipeclient-control) event before attempting to send data again. (However, please note that [ReadyToSend](#readytosend-event-pipeclient-control) is not fired when part of the data is successfully sent).

# SendFile Method ([PipeClient](#pipeclient-control) Control)

Sends the file over the connected pipe.

## Syntax

```text
pipeclientcontrol.SendFile FileName
```

## Remarks

This method sends the specified file to the server/process over the connected pipe.

Timeout must be set to a positive value so that the control will operate synchronously.

# SendLine Method ([PipeClient](#pipeclient-control) Control)

This method sends a string followed by a newline.

## Syntax

```text
pipeclientcontrol.SendLine Text
```

## Remarks

This method sends a string followed by a newline. This method is used to send data with line-oriented protocols. The line is followed by CRLF (*Chr$(13) & Chr$(10)*) .

Please refer to the [GetLine](#getline-method-pipeclient-control) method and [SingleLineMode](#singlelinemode-property-pipeclient-control) property for more information.

# SendText Method ([PipeClient](#pipeclient-control) Control)

This method sends text over the connected pipe.

## Syntax

```text
pipeclientcontrol.SendText Text
```

## Remarks

This method sends the specified text to the server. To send binary data, use the [SendBytes](#sendbytes-method-pipeclient-control) method instead.

When [Timeout](#timeout-property-pipeclient-control) is set to 0 the control will behave asynchronously. If you are sending data to the receiving process faster than it can process it, the outgoing queue might fill up. When this happens, the control fails with error 25036: "[10035] Operation would block" (WSAEWOULDBLOCK). You can trap this error, and then try to send the data again. The [BytesSent](#bytessent-property-pipeclient-control) property shows how many bytes were sent (if any). If 0 bytes were sent, then you can wait for the [ReadyToSend](#readytosend-event-pipeclient-control) event before attempting to send data again. (However, please note that [ReadyToSend](#readytosend-event-pipeclient-control) is not fired when part of the data is successfully sent).

# Connected Event ([PipeClient](#pipeclient-control) Control)

Fired immediately after a connection completes.

## Syntax

```text
Sub pipeclientcontrol_Connected()
```

## Remarks

When the connection is successfully established this event will fire.

# DataIn Event ([PipeClient](#pipeclient-control) Control)

This event is fired when data (complete lines) come in.

## Syntax

```text
Sub pipeclientcontrol_DataIn(Text As String, EOL As Boolean)
```

## Remarks

Trapping the DataIn event is your only chance to get the data coming from the other end of the connection. The incoming data are provided through the *Text* parameter.

*EOL* indicates whether or not the [EOL](#eol-property-pipeclient-control) string was found at the end of *Text*. If the [EOL](#eol-property-pipeclient-control) string was found, then *EOL* is True.

If *Text* is part of a data portion of length larger than [MaxLineLength](#MaxLineLength) with no [EOL](#eol-property-pipeclient-control) strings in it, then *EOL* is False. NOTE: This means that one or more DataIn events with *EOL* set to False can be received during a connection.

If the [EOL](#eol-property-pipeclient-control) property is "" (empty string), then *EOL* can be disregarded (it is always True).

NOTE: Events are not re-entrant. Performing time-consuming operations within this event will prevent it from firing again in a timely manner and may affect overall performance.

# Disconnected Event ([PipeClient](#pipeclient-control) Control)

Fired when a connection is closed.

## Syntax

```text
Sub pipeclientcontrol_Disconnected()
```

## Remarks

When the connection is closed this event will fire.

# Error Event ([PipeClient](#pipeclient-control) Control)

Fired when information is available about errors during data delivery.

## Syntax

```text
Sub pipeclientcontrol_Error(ErrorCode As Integer, Description As String)
```

## Remarks

The Error event is fired in case of exceptional conditions during message processing. Normally the control fails with an error.

The *ErrorCode* parameter contains an error code, and the *Description* parameter contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the [Error Codes](#trappable-errors-pipeclient-control) section.

# ReadyToSend Event ([PipeClient](#pipeclient-control) Control)

Fired when the control is ready to send data.

## Syntax

```text
Sub pipeclientcontrol_ReadyToSend()
```

## Remarks

The ReadyToSend event indicates that the underlying pipe is ready to accept data again after a failed send. The event is also fired immediately after a connection to the remote host is established.

# Config Settings ([PipeClient](#pipeclient-control) Control)

 The control accepts one or more of the following *configuration settings*. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the control, access to these *internal properties* is provided through the [Config](#config-method-pipeclient-control) method.

### PipeClient Config Settings

**AbsoluteTimeout**: Determines whether timeouts are inactivity timeouts or absolute timeouts.If **AbsoluteTimeout** is set to *True*, any method which does not complete within Timeout seconds will be aborted. By default, *AbsoluteTimeout* is *False*, and the timeout is an inactivity timeout.

**InBufferSize**: The size in bytes of the output buffer.This setting specifies the size in bytes of the output buffer. Small buffer sizes may reduce overall performance. The default value is "65536".

**MaxLineLength**: The maximum amount of data to accumulate when no EOL is found.[MaxLineLength](#MaxLineLength) is the size of an internal buffer, which holds received data while waiting for an [EOL](#eol-property-pipeclient-control) string.

If an [EOL](#eol-property-pipeclient-control) string is found in the input stream before [MaxLineLength](#MaxLineLength) bytes are received, the [DataIn](#datain-event-pipeclient-control) event is fired with the *EOL* parameter set to *True*, and the buffer is reset.

If no [EOL](#eol-property-pipeclient-control) is found, and [MaxLineLength](#MaxLineLength) bytes are accumulated in the buffer, the [DataIn](#datain-event-pipeclient-control) event is fired with the *EOL* parameter set to *False*, and the buffer is reset.

The default value is 2048 bytes. The maximum value is 65536 bytes.

**OutBufferSize**: The size in bytes of the input buffer.This setting specifies the size in bytes of the input buffer. Small buffer sizes may reduce overall performance. The default value is "65536".

**PipeDirection**: Determines the direction data flows.Pipe servers are sometimes configured to only send or only receive data (a direction), which can cause [Connect](#connect-method-pipeclient-control) to fail if [PipeDirection](#PipeDirection) is not set accordingly. Set this to match the direction of the pipe server. Valid values are:

|  |  |
| --- | --- |
| 1 | In. The server can only receive data. |
| 2 | Out. The server can only send data. |
| 3 | In/Out (default). The server can both receive and send data. |

### Base Config Settings

**CodePage**: The system code page used for Unicode to Multibyte translations.The default code page is Unicode UTF-8 (65001).

The following is a list of valid code page identifiers:

|  |  |
| --- | --- |
| Identifier | Name |
| 037 | IBM EBCDIC - U.S./Canada |
| 437 | OEM - United States |
| 500 | IBM EBCDIC - International |
| 708 | Arabic - ASMO 708 |
| 709 | Arabic - ASMO 449+, BCON V4 |
| 710 | Arabic - Transparent Arabic |
| 720 | Arabic - Transparent ASMO |
| 737 | OEM - Greek (formerly 437G) |
| 775 | OEM - Baltic |
| 850 | OEM - Multilingual Latin I |
| 852 | OEM - Latin II |
| 855 | OEM - Cyrillic (primarily Russian) |
| 857 | OEM - Turkish |
| 858 | OEM - Multilingual Latin I + Euro symbol |
| 860 | OEM - Portuguese |
| 861 | OEM - Icelandic |
| 862 | OEM - Hebrew |
| 863 | OEM - Canadian-French |
| 864 | OEM - Arabic |
| 865 | OEM - Nordic |
| 866 | OEM - Russian |
| 869 | OEM - Modern Greek |
| 870 | IBM EBCDIC - Multilingual/ROECE (Latin-2) |
| 874 | ANSI/OEM - Thai (same as 28605, ISO 8859-15) |
| 875 | IBM EBCDIC - Modern Greek |
| 932 | ANSI/OEM - Japanese, Shift-JIS |
| 936 | ANSI/OEM - Simplified Chinese (PRC, Singapore) |
| 949 | ANSI/OEM - Korean (Unified Hangul Code) |
| 950 | ANSI/OEM - Traditional Chinese (Taiwan; Hong Kong SAR, PRC) |
| 1026 | IBM EBCDIC - Turkish (Latin-5) |
| 1047 | IBM EBCDIC - Latin 1/Open System |
| 1140 | IBM EBCDIC - U.S./Canada (037 + Euro symbol) |
| 1141 | IBM EBCDIC - Germany (20273 + Euro symbol) |
| 1142 | IBM EBCDIC - Denmark/Norway (20277 + Euro symbol) |
| 1143 | IBM EBCDIC - Finland/Sweden (20278 + Euro symbol) |
| 1144 | IBM EBCDIC - Italy (20280 + Euro symbol) |
| 1145 | IBM EBCDIC - Latin America/Spain (20284 + Euro symbol) |
| 1146 | IBM EBCDIC - United Kingdom (20285 + Euro symbol) |
| 1147 | IBM EBCDIC - France (20297 + Euro symbol) |
| 1148 | IBM EBCDIC - International (500 + Euro symbol) |
| 1149 | IBM EBCDIC - Icelandic (20871 + Euro symbol) |
| 1200 | Unicode UCS-2 Little-Endian (BMP of ISO 10646) |
| 1201 | Unicode UCS-2 Big-Endian |
| 1250 | ANSI - Central European |
| 1251 | ANSI - Cyrillic |
| 1252 | ANSI - Latin I |
| 1253 | ANSI - Greek |
| 1254 | ANSI - Turkish |
| 1255 | ANSI - Hebrew |
| 1256 | ANSI - Arabic |
| 1257 | ANSI - Baltic |
| 1258 | ANSI/OEM - Vietnamese |
| 1361 | Korean (Johab) |
| 10000 | MAC - Roman |
| 10001 | MAC - Japanese |
| 10002 | MAC - Traditional Chinese (Big5) |
| 10003 | MAC - Korean |
| 10004 | MAC - Arabic |
| 10005 | MAC - Hebrew |
| 10006 | MAC - Greek I |
| 10007 | MAC - Cyrillic |
| 10008 | MAC - Simplified Chinese (GB 2312) |
| 10010 | MAC - Romania |
| 10017 | MAC - Ukraine |
| 10021 | MAC - Thai |
| 10029 | MAC - Latin II |
| 10079 | MAC - Icelandic |
| 10081 | MAC - Turkish |
| 10082 | MAC - Croatia |
| 12000 | Unicode UCS-4 Little-Endian |
| 12001 | Unicode UCS-4 Big-Endian |
| 20000 | CNS - Taiwan |
| 20001 | TCA - Taiwan |
| 20002 | Eten - Taiwan |
| 20003 | IBM5550 - Taiwan |
| 20004 | TeleText - Taiwan |
| 20005 | Wang - Taiwan |
| 20105 | IA5 IRV International Alphabet No. 5 (7-bit) |
| 20106 | IA5 German (7-bit) |
| 20107 | IA5 Swedish (7-bit) |
| 20108 | IA5 Norwegian (7-bit) |
| 20127 | US-ASCII (7-bit) |
| 20261 | T.61 |
| 20269 | ISO 6937 Non-Spacing Accent |
| 20273 | IBM EBCDIC - Germany |
| 20277 | IBM EBCDIC - Denmark/Norway |
| 20278 | IBM EBCDIC - Finland/Sweden |
| 20280 | IBM EBCDIC - Italy |
| 20284 | IBM EBCDIC - Latin America/Spain |
| 20285 | IBM EBCDIC - United Kingdom |
| 20290 | IBM EBCDIC - Japanese Katakana Extended |
| 20297 | IBM EBCDIC - France |
| 20420 | IBM EBCDIC - Arabic |
| 20423 | IBM EBCDIC - Greek |
| 20424 | IBM EBCDIC - Hebrew |
| 20833 | IBM EBCDIC - Korean Extended |
| 20838 | IBM EBCDIC - Thai |
| 20866 | Russian - KOI8-R |
| 20871 | IBM EBCDIC - Icelandic |
| 20880 | IBM EBCDIC - Cyrillic (Russian) |
| 20905 | IBM EBCDIC - Turkish |
| 20924 | IBM EBCDIC - Latin-1/Open System (1047 + Euro symbol) |
| 20932 | JIS X 0208-1990 & 0121-1990 |
| 20936 | Simplified Chinese (GB2312) |
| 21025 | IBM EBCDIC - Cyrillic (Serbian, Bulgarian) |
| 21027 | Extended Alpha Lowercase |
| 21866 | Ukrainian (KOI8-U) |
| 28591 | ISO 8859-1 Latin I |
| 28592 | ISO 8859-2 Central Europe |
| 28593 | ISO 8859-3 Latin 3 |
| 28594 | ISO 8859-4 Baltic |
| 28595 | ISO 8859-5 Cyrillic |
| 28596 | ISO 8859-6 Arabic |
| 28597 | ISO 8859-7 Greek |
| 28598 | ISO 8859-8 Hebrew |
| 28599 | ISO 8859-9 Latin 5 |
| 28605 | ISO 8859-15 Latin 9 |
| 29001 | Europa 3 |
| 38598 | ISO 8859-8 Hebrew |
| 50220 | ISO 2022 Japanese with no halfwidth Katakana |
| 50221 | ISO 2022 Japanese with halfwidth Katakana |
| 50222 | ISO 2022 Japanese JIS X 0201-1989 |
| 50225 | ISO 2022 Korean |
| 50227 | ISO 2022 Simplified Chinese |
| 50229 | ISO 2022 Traditional Chinese |
| 50930 | Japanese (Katakana) Extended |
| 50931 | US/Canada and Japanese |
| 50933 | Korean Extended and Korean |
| 50935 | Simplified Chinese Extended and Simplified Chinese |
| 50936 | Simplified Chinese |
| 50937 | US/Canada and Traditional Chinese |
| 50939 | Japanese (Latin) Extended and Japanese |
| 51932 | EUC - Japanese |
| 51936 | EUC - Simplified Chinese |
| 51949 | EUC - Korean |
| 51950 | EUC - Traditional Chinese |
| 52936 | HZ-GB2312 Simplified Chinese |
| 54936 | Windows XP: GB18030 Simplified Chinese (4 Byte) |
| 57002 | ISCII Devanagari |
| 57003 | ISCII Bengali |
| 57004 | ISCII Tamil |
| 57005 | ISCII Telugu |
| 57006 | ISCII Assamese |
| 57007 | ISCII Oriya |
| 57008 | ISCII Kannada |
| 57009 | ISCII Malayalam |
| 57010 | ISCII Gujarati |
| 57011 | ISCII Punjabi |
| 65000 | Unicode UTF-7 |
| 65001 | Unicode UTF-8 |

 The following is a list of valid code page identifiers for Mac OS only:

|  |  |
| --- | --- |
| Identifier | Name |
| 1 | ASCII |
| 2 | NEXTSTEP |
| 3 | JapaneseEUC |
| 4 | UTF8 |
| 5 | ISOLatin1 |
| 6 | Symbol |
| 7 | NonLossyASCII |
| 8 | ShiftJIS |
| 9 | ISOLatin2 |
| 10 | Unicode |
| 11 | WindowsCP1251 |
| 12 | WindowsCP1252 |
| 13 | WindowsCP1253 |
| 14 | WindowsCP1254 |
| 15 | WindowsCP1250 |
| 21 | ISO2022JP |
| 30 | MacOSRoman |
| 10 | UTF16String |
| 0x90000100 | UTF16BigEndian |
| 0x94000100 | UTF16LittleEndian |
| 0x8c000100 | UTF32String |
| 0x98000100 | UTF32BigEndian |
| 0x9c000100 | UTF32LittleEndian |
| 65536 | Proprietary |

**MaskSensitiveData**: Whether sensitive data is masked in log messages.In certain circumstances it may be beneficial to mask sensitive data, like passwords, in log messages. Set this to *True* to mask sensitive data. The default is *True*.

**UseInternalSecurityAPI**: Whether or not to use the system security libraries or an internal implementation. When set to *False*, the control will use the system security libraries by default to perform cryptographic functions where applicable.

Setting this configuration setting to *True* tells the control to use the internal implementation instead of using the system security libraries.

 This setting is set to *False* by default on all platforms.

# Trappable Errors ([PipeClient](#pipeclient-control) Control)

### PipeClient Errors

|  |  |
| --- | --- |
| 20402 | Failed to create event. |
| 20403 | Failed to create security descriptor. |
| 20404 | Error creating named pipe. |
| 20405 | Error connecting to named pipe. |
| 20406 | Error disconnecting named pipe. |
| 20409 | Error sending data. |
| 20411 | Invalid MaxLineLength value. |
| 20412 | Error reading data. |
| 20413 | Error invoking RegisterWaitForSingleObject. |
| 20414 | Operation would block. |
| 20415 | Named pipe does not exist. |
| 20416 | Named pipe is already connected. |
| 20417 | Error connecting to named pipe. |
| 20418 | Named pipe not connected. |
| 20420 | Unsupported operation, see error message for details. |