Member information

Specify the following information about the internal members of your opaque data type:
  • Name. Must be unique within the opaque data type.
  • Data structure. Select from the list, which includes any extended data types you have defined or imported in the project and the data structures that correspond to the programming language you choose.
  • Array size. Specifies the number of components and subcomponents.
The following table maps the DataBlade® API data structures listed in the Opaque Type wizard to their external programming language equivalents.
DataBlade API data types C and ESQL/C data types ActiveX data types
gl_wchar_t char BSTR
mi_boolean boolean BOOL
mi_char char BSTR
mi_char1 char BSTR
mi_date int BSTR
mi_datetime dtime_t BSTR
mi_decimal dec_t BSTR
mi_double_precision double double
mi_int1 char short
mi_int8 ifx_int8_t BSTR
mi_integer int, long long
mi_interval intrvl_t BSTR
MI_LO_HANDLE ifx_lo_t
mi_money dec_t BSTR
mi_numeric dec_t BSTR
mi_real float double
mi_smallint short short
mi_string char BSTR
mi_unsigned_char1 unsigned char short
mi_unsigned_int8 ifx_int8_t BSTR
mi_unsigned_integer long
mi_unsigned_smallint uint2 short
mi_wchar uint2 BSTR
If you choose to create a variable-length opaque data type, a member is automatically added as an mi_int1 of variable size. Change the mi_int1 data structure to be the one you need. Be sure to list the variable-length member last.
Tip: If you create an opaque type with a member of type MI_LO_HANDLE, you can test for the existence of a particular sbspace when your DataBlade module is being registered in a database by using BladeManager.