Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 6 of 6 total |
17 digit numbers in a dbisam table |
Tue, Nov 28 2006 12:55 PM | Permanent Link |
"Amber Earles" | I am using DBISam tables (version 4.01) to store PLU (product lookup codes).
One of our new cash registers just came out with a 17 digit code. I am using a ftfloat to store the number and with the 17 digit codes they are returned in scientific notation. Is there a way to store/display the 17 digit number fully? Thank you very much for your time. If you need more information just let me know. Take care. Amber Earles PC/POLL SYSTEMS |
Tue, Nov 28 2006 1:54 PM | Permanent Link |
"Ivan Sine" | I use a string to store my long rfid numbers
|
Tue, Nov 28 2006 1:57 PM | Permanent Link |
"Amber Earles" | Thanks for the quick reply. I was hoping to avoid that if possible just
because we have a lot of other programming areas using those codes and just for basic sorting, etc. But, that might be the only option. Take care. "Ivan Sine" <ivan@nospamorhamag2networks.com> wrote in message news:23F6DE15-EB54-44B4-8EBC-83137D90C62B@news.elevatesoft.com... > I use a string to store my long rfid numbers > |
Tue, Nov 28 2006 3:36 PM | Permanent Link |
Sean McCall | Amber,
A float field returns its value as a Double and this type only has 15-16 significant digits, so you cannot reliably store a 17 digit code in this type of field. Sorry, but sounds like you might need to convert field types. Can't remember how many significant digits are in a ftLargeInt (64 bit integer) field, but I suspect that would give you plenty of room to grow. Good luck, Sean Amber Earles wrote: > I am using DBISam tables (version 4.01) to store PLU (product lookup codes). > One of our new cash registers just came out with a 17 digit code. I am > using a ftfloat to store the number and with the 17 digit codes they are > returned in scientific notation. Is there a way to store/display the 17 > digit number fully? Thank you very much for your time. If you need more > information just let me know. Take care. > > Amber Earles > > PC/POLL SYSTEMS > > |
Tue, Nov 28 2006 3:43 PM | Permanent Link |
"Donat Hebert \(Worldsoft\)" | LargeInt would cover to 18 digits if that's an option for you. (Still
numeric) "Amber Earles" <amber@pcpoll.com> wrote in message news:73961188-C189-48BA-8243-B609F2FF8BC5@news.elevatesoft.com... > Thanks for the quick reply. I was hoping to avoid that if possible just > because we have a lot of other programming areas using those codes and > just > for basic sorting, etc. But, that might be the only option. Take care. > > > > > "Ivan Sine" <ivan@nospamorhamag2networks.com> wrote in message > news:23F6DE15-EB54-44B4-8EBC-83137D90C62B@news.elevatesoft.com... >> I use a string to store my long rfid numbers >> > > |
Tue, Nov 28 2006 6:04 PM | Permanent Link |
"Amber Earles" | Thanks guys. I will give it a try. Take care.
Amber "Sean McCall" <someone@somewhere.net> wrote in message news:A50A9B7A-ED00-4699-80AB-97B7621EF2EE@news.elevatesoft.com... > Amber, > > A float field returns its value as a Double and this type only has 15-16 > significant digits, so you cannot reliably store a 17 digit code in > this type of field. Sorry, but sounds like you might need to convert > field types. Can't remember how many significant digits are in a > ftLargeInt (64 bit integer) field, but I suspect that would give you > plenty of room to grow. > > Good luck, > > Sean > > > > Amber Earles wrote: > > I am using DBISam tables (version 4.01) to store PLU (product lookup codes). > > One of our new cash registers just came out with a 17 digit code. I am > > using a ftfloat to store the number and with the 17 digit codes they are > > returned in scientific notation. Is there a way to store/display the 17 > > digit number fully? Thank you very much for your time. If you need more > > information just let me know. Take care. > > > > Amber Earles > > > > PC/POLL SYSTEMS > > > > |
This web page was last updated on Sunday, May 19, 2024 at 08:46 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |