What field type other than text can Access hold a 14 digit number?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

just trying to make a table for an ID number thjat is 14 digits long and
don't want to have to use text in less i have too. Information would br
greatly appericated
 
ARYVELLA said:
just trying to make a table for an ID number thjat is 14 digits long
and don't want to have to use text in less i have too. Information
would br greatly appericated

Double Stores numbers from
-1.79769313486231E308 to
-4.94065645841247E-324
for negative values and from
4.94065645841247E-324 to
1.79769313486231E308 for positive values. 15
 
What's the matter with using text type? If it's disk space you are concerned
with (which would only ever add up to something significant with a large
database) set the field size to 14. So long as you are controlling the input
(i.e. restricting letters for example) this field would "appear" to be a
number type.
 
it is whole number like : 23650000227970

visual basic searches number data types much faster then text
 
currency ought to do it (all versions)
number(14,0) in newer versions

pieter
 
kabaka said:
What's the matter with using text type? If it's disk space you are
concerned with (which would only ever add up to something significant
with a large database) set the field size to 14. So long as you are
controlling the input (i.e. restricting letters for example) this
field would "appear" to be a number type.

Yea, I did not read that "ID number" Generally for ID numbers text is
not only as good, but better since you can easily have leading zeros, or add
numbers or spaces; all of which the boss will want next month.
 
Per Joseph Meehan:
Yea, I did not read that "ID number" Generally for ID numbers text is
not only as good, but better since you can easily have leading zeros, or add
numbers or spaces; all of which the boss will want next month.

I'm guessing the 14-digit number is going to be the table's PK.

Has anybody tried using GUIDs for this purpose? Quite a bit bigger, but maybe
easier to use in some cases.
 
Per Brendan Reynolds:
Michael Kaplan has an article on that subject at the following URL ...
http://www.trigeminal.com/usenet/usenet011.asp?1033

I guess that pretty much settles the question....-)

When I was dabbling in GUIDS, what turned me off was the size of the canonical
presentation. Even though I'd never expose a PK in the UI, it seemed awfully
unweildy for debugging - i.e. manually beating through tables and checking data.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top