Known Limitations and Problems        

        The following problems are discovered. Once we find a bug, we will try to solve it. You are encouraged to come to this web site to download the latest OleDBPro module. If a bug can't be fixed by us, we'll post it here. Please tell us the problems you found, which are very important to us.

        Here are known problems:

1. If an original BLOB data type is DBTYPE_WSTR and data type is forced to DBTYPE_STR, CRBase::GetLength and CRBase::GetLenStatus will give a wrong length with MS Jet provider 4.0. However, MS Jet Provider 3.51 doesn't has this problem. This is a bug from Jet 4.0 provider.

2. For both Jet providers 4.0 and 3.51, CRBase::GetLenStatus can't get the correct length if a raw column data type is DBTYPE_I4 while input nDBType is either DBTYPE_STR or DBTYPE_WSTR. This is a bug from Jet providers.

3. The following compiling messages will come out when a _bstr_t object is defined in a cpp file with Borland C++ builder 5:
           Error: Unresolved external ' __stdcall _com_util::ConvertStringToBSTR(const char *) referenced from test.obj.
           Error: Unresolved external ' __stdcall  _com_issue_error(long) referenced
   from test.obj.
   You could use CComBSTR instead of _bstr_t with Borland C++ builder.