A full 32bit Integer is in the range of -2147483648 to +2147483647 with
the unsigned version being a LongInt +4294967295.
RBase's smaller range is a legacy issue that at the moment cannot be
changed.... easily.
----- Original Message -----
From: "jan johansen" <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Friday, July 10, 2009 12:09 PM
Subject: [RBASE-L] - Re: Large integer values in Rbase v8
Bill,
I ran into this problem a couple of months ago. On the face value you
would
think it
would hold what you needed. My challenge was I needed to create an invoice
number
for an automatic process. The idea was to take the 4 digit cust id and add
the 6 digit
date to it. So an invoice for customer 2090 and today would look like
this.
2090090710
However an R:BASE integer is defined as such
INTEGER
·Holds whole numbers in the range of ±1,999,999,999
·Delimiters (such as commas) cannot be used in entry
·R:BASE reserves four bytes of internal storage space
So my converted would look like this to R:BASE 2,090,090,710 which exceeds
the maximum definintion for an integer.
Explains the problem but doesn't help you right now.
Jan Johansen
Authorized R:BASE Developer
-----Original Message-----
From: "Bill Niehaus" <[email protected]>
To: [email protected] (RBASE-L Mailing List)
Date: Fri, 10 Jul 2009 10:57:45 -0500
Subject: [RBASE-L] - Large integer values in Rbase v8
I am trying to track some large numbers and planned to use an integer
type.
The number can be 10 digits long but can not have any decimal values (all
whole numbers). It seems like an integer works ok for an 9 digit number
but
does not work for a 10 digit number. I'm not sure how I can confirm this.
Should an integer handle a 10 digit number and if not, what is a better
option for a 9 digit number.
Thanks.
Bill
