Hello,

I am looking for a workaround for a bug or limitation which I read about a long time ago, but cannot remember where.
When retrieving a cursoradapter from an Oracle database through OleDB (Oraoledb.Oracle provider), the number fields with precision>=20 don't seem to be translated correctly. That includes fields declared as NUMBER, without specified precision. For instance, when creating a CA called "test" out of the query "SELECT bytes FROM user_extents", the datatype of "test.bytes" is "C", although the bytes field is declared to NUMBER in Oracle.
This problems happens only with the CA. If with the same query I directly use an ADO recordset to get the values, the datatype is then "N" as it should.

What should I do ? Is it possible to change the datatype in the CA with something like DBSETPROP ? I cannot change the Oracle precision since I am querying the Oracle data dictionary.

Best regards,

David