How would it be the best / most effective / less memory consuming way to store a 64 bits integer into a Jet Engine database? I’m pretty sure their integers are 32 bits.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
The largest integer MSAccess supports is a
NUMBER(FieldSize=LONG INTEGER) typebut this is not 64 bits.
http://msdn.microsoft.com/en-us/library/ms714540(v=vs.85).aspx
To store numbers as large as 64 bits you will need to use the
DOUBLEorDECIMALtype, but will not have “integer precision” withDOUBLEand you have overhead withDECIMALAlternatively you could use a
CURRENCYtype and disregard decimals.http://www.w3schools.com/sql/sql_datatypes.asp
For more details on the nuances of all data types you can look here:
http://office.microsoft.com/en-us/access-help/introduction-to-data-types-and-field-properties-HA010233292.aspx
EDIT: Though you will have a limited number of significant digits in
DOUBLEas pointed out by @ho1 in the comments below.You can make
CURRENCYwork by inferring the digits in code if you are pressed for disk storage space but your best bet is probablyDECIMAL