Type Mismatch error

[jrl]

Background: I corrected the mismatch issue by changing my field definition to a float (from integer) when the type mismatch error was received.

This worked... for most of my users.

Several users still received a mismatch error when querying the database. For this situation I used the workaround to "add zero" (select field+0, ...) to the query.

So my question is, with all things remaing equal (same machine, same code) except the oracle logon information, does anyone have any insight to what could be different between oracle accounts to cause the queried data to be seen as a float by most users, but as an integer by several others?

 

[Marco Kalter]

Is this on the same database? I can only imagine a difference if the database version is different.

 

[jrl]

Yes, same database, same data even. That is what is so strange about it.

 

[Marco Kalter]

You could create a little application with a TOracleQuery with the same SQL, execute it, and check what the TOracleQuery.FieldScale and FieldPrecision functions return for this field. These 2 properties determine if a field is represented as an integer or float.

If they are the same, there must be something wrong with the application. If they are different, then there must be a difference in the Oracle Client or Server.