1.1.15 VarBinary

VarBinary is a variable-length binary field, with a maximum length between 1 and 32,767.

VarBinary fields are used to store binary data. This data is not subject to codepage conversion.

Field Definition Rules

Rules for defining a VarBinary field in the repository are:

Length	VarBinary fields may be 1 to 32,767 in length. VarBinary fields have no decimals.
Valid Keyboard Shift	Blanks
Allowed Attributes	AB, ASQN, CS, FE, ND, RA, RL, RLTB.
Edit Mask	Not allowed.
Default	*SQLNULL. ASQN will be enabled by default.

There is NO difference between Binary and VarBinary except how they are stored in the database.

Partition Type	RDMLX Enabled Partition
Files	VarBinary fields may only be used in RDMLX Files. VarBinary fields may be used as real fields. VarBinary fields may not be used as key fields.
Logical Views	VarBinary fields may not be used as key fields.
Virtual Fields	VarBinary fields may be used with Code Fragment Virtual Fields.
Predetermined Join Fields	VarBinary fields may be used for lookup predetermined joined fields.
RDML Commands	DEF_HEAD, DEF_FOOT, DEF_BREAK, and DEF_LINE will not support printing of fields of type VarBinary. A FFC error will be generated if these VarBinary fields are used. VarBinary fields are manipulated as if they are String fields except where sensitivity to their Binary characteristics will be incorporated.
Built-In Functions	When used in Built-In Functions, VarBinary fields are classified as their own types and are not valid for numeric or alpha arguments.
Special Values	NULL, NAVAIL, *REMEMBERED_VALUE
Conversion	VarBinary fields may be converted to character type fields. Refer to Field Type Conversions.

There is no working field type for VarBinary fields.
If an SQL WHERE clause will/may be generated by a condition, these field types may only be compared to *NULL or *SQLNULL; any other comparison will be rejected.