4.10.4 Unicode

All string parameters to the FDT interfaces are BSTRs and are therefore UNICODE strings.
Microsoft MIDL Version 3.0 or later is required to correctly compile the IDL code and generate proxy/stub software. Microsoft Windows NT 4.0 (or later), or Windows 95 with DCOM support is required to properly handle the marshaling of FDT parameters.
Note that in order to implement FDT software that will run on both Microsoft Windows NT and Microsoft Windows 95, it is necessary for these components to test the platform at runtime. In the case of Microsoft Windows 95, usually the conversion of any strings to be passed to Win32 from UNICODE to ANSI needs to be done. Visual Basic makes this conversion implicitly.
The only limitation within this specification is that a NUL character (i.e.0) is only allowed as the last character of any BSTR method parameter to prevent conversion errors (UNICODE<->ANSI, uppercase<->lowercase, etc.) within the database.