Thanks, Helen.

>Definitely! :-) by an order of 3. Numeric(18,2) will store values up

to a non-negotiable limit of >92,233,720,368,547,758.07 whereas your
highest number with numeric(18,5) is 92,233,720,368,547.75807

I'm changing the output parameters of my selectable stored procedures
(used for reporting purposes) from decimal(18, 5) to decimal(18, 2)
which is help a lot (by the order of 1000).
If I were to convert the fields in the table, I take it it won't be a
simple sql statement, as I'd probably have to create new fields and copy
existing data across to the new fields. And then the reports would crash
when the price is multiplied by the quantity anyway (so maybe it is a
good thing at the end of the day that you can't get those huge figures
in in the first place...)

>No. There are no plans in the pipeline to support 128-bit integers in

Firebird 2.5 or Firebird 3. About >the future - who knows?

Please, please, one day. ;-)

>You can use double precision to stretch the boundaries, provided your

dynamic SQL and PSQL deal >accurately enough with the issues of rounding
and scale.

Real and types plus accountancy apps = nightmare.
I learnt that the hard way unfortunately.

Thanks
Maya