No, Access is far more intelligent than that.
Just because you have a text field that stores 255 characters does NOT mean
Access uses up 255 bytes for every record. It uses bytes only for the actual
characters that are there.
If the Unicode Compression is not enabled for the field, it uses 2 bytes for
each actual character in the field, but that applies only in Access 2000 and
later. Further, there is some overhead for the table itself, and some
overhead for each field in the table on top of the space to store the data.
This includes 7 bytes for overhead for each record, 1 byte for each
variable-length column plus 1 additional byte for every 256 bytes of total
space occupied by all the variable-length columns, and 1 byte for the
fixed-size columns (yes/no, Number, ...) + the size of the fixed-width
columns (e.g. 4 bytes for Long, 8 bytes for double, 8 bytes for Date/Time, 8
bytes for Currency).
Then if you do have an OLE Object storing graphic data, it starts to get
really messy. So the short answer is: No, not easily.