> Yes, sorry about that - you may have an issue with changing the
> value.  I'm afraid you'll have to wait until the bug fixes are ready,
> which hopefully won't be much longer.

No problem--I've already replaced the function with a stored procedure.

Thanks!

--
David Cornelius
CorneliusConcepts.com

David


From Tim's answer I think you were nearer than I was, but the important thing is its being fixed.

Roy Lambert

> However, the root of the problem was that the Information schema was
> returning incorrect Scale information via the Functions table.  This
> was also the cause of the display issue in the EDB Manager.
> Furthermore, there was an issue with the loading the Scale and
> Collation information for return values from functions.

I just realized the extent of this tonight.  After hours of
trouble-shooting a round-off error reported by my customer, I realized
the same function that was plaguing me before (which I replaced with a
stored procedure call) was causing a problem purely at the database
level (no Delphi components involved) in another part of the
application.

I had a trigger on a header table that on update, would call a "details
total" function that gets the total of Price * Qty from the related
details table.  I figured the problem with the function was limited to
displayed values through the EDBQuery component in Delphi, but even
though I had the scale set to 3 in the function, it was always rounding
it off to the nearest whole dollar amount.

So I came back and re-read your statement and realized this could have
farther-reaching affects than just display.  Wow--I'm going to stay
away from functions for a bit!  This cost me a lot more sleep tonight.
Ugh.

--
David Cornelius
CorneliusConcepts.com

David,

<< So I came back and re-read your statement and realized this could have
farther-reaching affects than just display.  Wow--I'm going to stay away
from functions for a bit!  This cost me a lot more sleep tonight. Ugh. >>

Just to clarify - this is only an issue for functions that return a DECIMAL
with a defined scale greater than 0, and will be corrected shortly, so after
that you will have no problem using such functions.

--
Tim Young
Elevate Software
www.elevatesoft.com

> Just to clarify - this is only an issue for functions that return a
> DECIMAL with a defined scale greater than 0, and will be corrected
> shortly, so after that you will have no problem using such functions.


Right.  After posting this, I looked at another function that works just
fine.  It's the TableVersion function that I posted on .extensions a while
back.  It works because it returns FLOAT.

But I am a little gun-shy right now.  

--
David Cornelius
CorneliusConcepts.com