At 10:30 AM 29/08/2005 +0700, you wrote:

>In the original version of sample code of "Client/Server concept",
>content stringlist property
>of DmEmployee.ibSalaryHistoryTable.FieldsDisplayFormat are :
>
>PERCENT_CHANGE=###.####
>OLD_SALARY=$###,###,##0.00
>NEW_SALARY=$###,###,##0.00
>
>But ... it doesn't work, and still release error messages frequently "4.25
>(or something float value) is not a valid integer value".

OK, these formats look OK for extended or float types. Going by the small
value of 4.25, I suppose the field that is throwing the exception
is PERCENT_CHANGE. The OLD_SALARY field is a numeric(18,2), while the
other field is a computed field.

Could you get closer to where the exception is being thrown?

>If I delete all contents of FieldsDisplayFormat, error message dissapear
>though value appearance of float/numeric field column not such as I expect.

No, it would be ugly. I'll take a look at that code for you. It is very
old stuff. There's a chance that it might have something in there that
doesn't work properly with the ODS 10 data types.

Would you respond back to the list, telling me what versions of database
server and IBO you are using?

For the money values, you can set the Currency attribute. This will sort
out the appearance of the decimal part of a FP number, but it doesn't have
the ability to display symbols.

Helen