Mismatch error using lookup fields

[anthony anderson]

Hi, I'm using Oracle 9.2.0.1 and a NUMBER field is declared in Delphi as a TFloatField but as soon as I use a 9.2.0.7 database I get a type mismatch. If then I re-add the field in Delphi but this time attached to the later Oracle version the field is added as a TIntegerField. This is causing major problems as the dataset will not open! Has anyone seen this before or know of a solution? Thanks!

 

[Marco Kalter]

I assume that this number(6) field is used in a function within a query? For example in a union, or in some arithmetic expression? Sometimes different Oracle Server versions can report different scale and/or precision for such queries, which can result in an integer field in one database, and a float field in another. The only workaround is to use a dummy arithmetic expression (e.g. field + 0.0) to force a float field in all situations.