SevalUcar
1st May 2002, 11:37
Problem: Cannot process "big numbers"
that have more than 15 digits.
Area : BaaN Tools, probably DB Driver level
Env. : BaaN IVc3 MCR
(No pathes has been applied since 1st of Jan. 2000),
Oracle 7.3, Windows NT Ent., MSCS,
P.Owner: seval.ucar@toros.com.tr
We are such a rich country (!) and our money has exceeded more than 15 digits.
Oracle 7.3 can handle such big amounts but BaaN IV cannot (may be BaaN V too). More than 15 digit number cannot be processsed correctly in BaaN IV (technical detail is below). We suppose that it had been limited in BaaN DB driver level.
To understand the problem any developer can create a table in BaaN and try process a number like 999.999.999.999.999.999 by BaaN Tools (simple sum up more than 10 numbers like this). Then do the same by Oracle tools and compare the results.
Could any of you using BaaN IV (and BaaN V too) try this and inform me about the result?
We don't know whether this could be solved on DB driver level easiliy or...
Can any of you have idea on how to overcome this limitation?
Thank you.
A bit more technical....
We've created an example table, tfxxx900, that have two fields named as lino (domain is tfgld.lino) and amnt (domain is tfgld.amnt). The table has one index named "index1" on field "lino".
We've added one record in the table and "tfxxx900.lino=1" and "tfxxx900.amnt=1234"
We've generated a session like
declaration:
table ttfxxx900
extern domain tfgld.lino hold.lino
extern domain tfgld.amnt hold.amnt
functions:
hold.lino=1
hold.amnt=1234567890123456789"
select tfxxx900.* from tfxxx900 for update
where tfxxx900._index1={:hold.lino}
selectdo tfxxx900.amnt=hold.amnt
db.update(ttfxxx900,db.retry)
endselect
commit.transaction()
If you can look at session ttaad4100 and see correct value there is no problem in your system.
We cannot see the right value.:confused:
that have more than 15 digits.
Area : BaaN Tools, probably DB Driver level
Env. : BaaN IVc3 MCR
(No pathes has been applied since 1st of Jan. 2000),
Oracle 7.3, Windows NT Ent., MSCS,
P.Owner: seval.ucar@toros.com.tr
We are such a rich country (!) and our money has exceeded more than 15 digits.
Oracle 7.3 can handle such big amounts but BaaN IV cannot (may be BaaN V too). More than 15 digit number cannot be processsed correctly in BaaN IV (technical detail is below). We suppose that it had been limited in BaaN DB driver level.
To understand the problem any developer can create a table in BaaN and try process a number like 999.999.999.999.999.999 by BaaN Tools (simple sum up more than 10 numbers like this). Then do the same by Oracle tools and compare the results.
Could any of you using BaaN IV (and BaaN V too) try this and inform me about the result?
We don't know whether this could be solved on DB driver level easiliy or...
Can any of you have idea on how to overcome this limitation?
Thank you.
A bit more technical....
We've created an example table, tfxxx900, that have two fields named as lino (domain is tfgld.lino) and amnt (domain is tfgld.amnt). The table has one index named "index1" on field "lino".
We've added one record in the table and "tfxxx900.lino=1" and "tfxxx900.amnt=1234"
We've generated a session like
declaration:
table ttfxxx900
extern domain tfgld.lino hold.lino
extern domain tfgld.amnt hold.amnt
functions:
hold.lino=1
hold.amnt=1234567890123456789"
select tfxxx900.* from tfxxx900 for update
where tfxxx900._index1={:hold.lino}
selectdo tfxxx900.amnt=hold.amnt
db.update(ttfxxx900,db.retry)
endselect
commit.transaction()
If you can look at session ttaad4100 and see correct value there is no problem in your system.
We cannot see the right value.:confused: