Re: Access's datatypes
From: Bonj (Bonj_at_discussions.microsoft.com)
Date: 10/29/04
- Next message: Bob Butler: "Re: Set objEct = Nothing"
- Previous message: alpine: "Re: Set objEct = Nothing"
- In reply to: Rick Rothstein: "Re: Access's datatypes"
- Next in thread: Allen Browne: "Re: Access's datatypes"
- Reply: Allen Browne: "Re: Access's datatypes"
- Reply: Ralph: "Re: Access's datatypes"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 29 Oct 2004 07:48:09 -0700
mmmm... it *nearly* is. I basically could do with a list of all the
sub-datatypes within 'Number' - and how many bytes they take up. For
instance, how many bytes does a "Number (Single)" (SQL_REAL) take up? It's
just to show somebody who's convinced that we can save space in our
(*apparently* space-critical) Access system by using a smallint divided by
1000 instead of a float for percentages and what not, and he just will not
let it drop until I prove that we are absolutely optimizing the size of the
DB. (the Access database is only 77MB at the moment...not exactly bursting at
the seems, but apparently it will eventually expand such that we've got so
many databases they won't fit on a CD, which is how they are going to be
distributed.)
If I can show that a float takes up the same size as a 16-bit int, then I
won't have to bother changing it, which would be a right P.I.T.A as it will
probably have absolutely zero impact on anything if I do - but I suspect it
takes up 32 bits.... (sigh)... but still. I have to look into it.
- Next message: Bob Butler: "Re: Set objEct = Nothing"
- Previous message: alpine: "Re: Set objEct = Nothing"
- In reply to: Rick Rothstein: "Re: Access's datatypes"
- Next in thread: Allen Browne: "Re: Access's datatypes"
- Reply: Allen Browne: "Re: Access's datatypes"
- Reply: Ralph: "Re: Access's datatypes"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|