> Yes, this was fixed but has resurfaced... a dratted nuiscance
> and time waster. :-) I have brute-force patched the source
> for my purposes while I try to figure out why the code is there.

Can you please elaborate on what you consider to be a problem. It
cant be fixed if we dont know what you expect.

Is there some reason why you dont want NUMERIC/DECIMAL fields to be
implemented as BCD? If you are treating such fields as float/double
at the client, why are you not using float/double at the database?


Geoff Worboys
Telesis Computing