On 4/24/06, Gabriel Mahiques <[EMAIL PROTECTED]> wrote:
>
> but, when the fields are float type, this error don't happen. When the
> fileds are float the result is the correct (if I have 1.2569 in the
> table, in the application I see "1.2569".)
Ok, so, I didn't quite understand. Let me see, you c
but, when the fields are float type, this error don't happen. When the
fileds are float the result is the correct (if I have 1.2569 in the
table, in the application I see "1.2569".)
Daniel da Veiga escribió:
Check the way your forms deal with the data from the resultset, any
implicit conversi
Check the way your forms deal with the data from the resultset, any
implicit conversion? Maybe a declaration of type that is casting
another type for the value returned from the resultset.
Also check this:
http://dev.mysql.com/doc/refman/5.0/en/precision-math-decimal-changes.html
On 4/24/06, Gabr
Hi.
A Brief description about my problem.
We have many applications development in Visual Basic 5. These
applications read data from MySQL 4.0 installed on Linux (and odbc
3.51.06). Many fields in our tables are in decimal format.
Last weekend we installed MySQL 5 on Linux
When we ran the appli
