--- In IBObjects@yahoogroups.com, "stanw1950" <stanw@e...> wrote:

> --- In IBObjects@yahoogroups.com, "pict100" <pict100@y...> wrote:
> > We had a similar problem until we changed all
> > double precision fields into numeric(18,4)
> > It may be something else in your application.
> > The fastest way to change all this was to
> > declare a new domain :
> >
> > CREATE DOMAIN "T_CURRENCY" AS NUMERIC(18, 4);
> >
> > and in metadata now we have :
> >
> > "CREDIT" T_CURRENCY ,
> >
> > INSTEAD OF
> >
> > "CREDIT" DOUBLE PRECISION,
> >
> >
> > Now it works flawlessly.
> >
> > Hope that helped
> >
> > Nx
>
> Thanks for the suggestion. That may be the way to go if bug is not
> fixed. I have a significant number of float fields (using Interbase
> Dialect 1)) so it would be a significant project. I just don't

think

> that I should have to change anything unless Jason intentionally
> decided that he didn't want to deal with float fields anymore. If
> that was the case then he should have warned his users that float
> fields don't work properly in release 4.3aa. However, I don't think
> that this was his intent and that this is just a bug.
>
> Stan

Jason,
I first posted this on Friday and haven't got a response from you.
This is still a big issue with us. Is this, or is this not a bug? If
its a bug, will it be fixed? We are a registered (ie we paid) user of
IBObjects and would appreciate a reply. Thanks.