ok I exagerated it's only 521 more forms, a lot
of them look like each other - hmmmm I wonder.....
-----Original Message-----
From: Tony Blomfield <[EMAIL PROTECTED]>
To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
Date: Tuesday, 25 May 1999 10:36
Subject: Re: [DUG]: Changing Numeric Column in IB5Effectivly this means you now have double precision storage. (Up to 9 positions are stored as Integer I beleive) Thus I guesse you can expect in some circumstances to get small rounding errors which may result in your totals being out by the odd cent, particulary where you are summing extended results.600 more? We better have a chat some time.Cheers,Tony.-----Original Message-----
From: Willie Juson <[EMAIL PROTECTED]>
To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
Date: Tuesday, 25 May 1999 21:42
Subject: [DUG]: Changing Numeric Column in IB5Hi all,we've just discovered that Numeric(8,4) in our database design is sort 4 or five digits left of the decimal point and 4 decimal places (not 8 and 4 as initially thought). Not a big problem except the app has gone live in an "everything must happen yesterday week" industry and for some reason our users want some reports that total properly - demanding sods.I've done some modify scripts (IB 5.5) changing several columns from (8,4) to (12,4) and tested some of our forms/reports against the new database structure - so far with no problems - is anyone aware of any holes we can unsuspectingly fall into doing this. I know increasing/decreasing string field sizes causes problems especially with dbgrids, but so far this numeric change seems to have had no impact on our forms - except some reports no longer give an overflow error . There are approx 290 forms and I simply don't have time to exhaustively test each one (and/or sleep, eat and breath and write the other 600 forms we need to finish the app by april 1st this year!) so any comments would be much appreciated.regards
