Subject | Problem with Displayformat |
---|---|
Author | Helmut Steinberger |
Post date | 2003-11-27T13:04:45Z |
Since I updated to IBO4.3 I got a problem with the displayformat.
I have a table with a field declared like that:
field1 numeric (6, 2)
When I use this field in a grid and setting the displayformat for this
field in the fieldsdisplayformat like that:
field1=###,##0.00
I get an error when accessing displaytext for this field, if the field
contains a value which has decimals.
Before upgrading to IBO4.3 it worked well.
I used the debugger and found out, that in the getasextended method of
the ib_column causes the problem. In the SQLScale for this column the
value is 0, which leads to a a conversion of the tmpS (containing for
example 2.5) by strtoint.
I compared it with the getasextended of IBO4.2 and found out, that
there was no such query for SQLScale.
I changed it now in IBO4.3 to the state it was in 4.2 and it works
well.
What is the reason for the change and should I expect more such
"surprises" when updating to newer versions of IBO?
It is very annoying, when every update to a newer version leads to new
problems, which sometimes are discovered weeks after the update, when
hidden in a part of the application, which is not used that often.
cu
Helmut
I have a table with a field declared like that:
field1 numeric (6, 2)
When I use this field in a grid and setting the displayformat for this
field in the fieldsdisplayformat like that:
field1=###,##0.00
I get an error when accessing displaytext for this field, if the field
contains a value which has decimals.
Before upgrading to IBO4.3 it worked well.
I used the debugger and found out, that in the getasextended method of
the ib_column causes the problem. In the SQLScale for this column the
value is 0, which leads to a a conversion of the tmpS (containing for
example 2.5) by strtoint.
I compared it with the getasextended of IBO4.2 and found out, that
there was no such query for SQLScale.
I changed it now in IBO4.3 to the state it was in 4.2 and it works
well.
What is the reason for the change and should I expect more such
"surprises" when updating to newer versions of IBO?
It is very annoying, when every update to a newer version leads to new
problems, which sometimes are discovered weeks after the update, when
hidden in a part of the application, which is not used that often.
cu
Helmut