hi
none really. an integer is 1 byte, a long is 2 bytes. when dos first came
out and IMB decided that 64000 byte would be all the memory anyone would ever
need, 1 byte may have been signifcant but today where memory is measured in
megabyes and gigabyles, 1 byte is insignificant.
an integer will represent a number value of 32767(pos or neg). the number
value of today's date is 40222 meaning you would get overflow errors trying
to assign a date to a variable dimmed as an integer. personally i never use
integer anymore.
in vb help, type in "data types" and view the table of data types. the
largest is variant which is about 20 bytes which in my opion is still fairly
insignificant.
I wouldn't really worry about it anymore. only if and when you do get an
overflow error would you need to think about it.

regards
FSt1

"Neal Zimm" wrote:

Hi All,
I come from a day when storage was a LOT dearer than it is today.

I use Integer or Long for whole # values 'cuz I read once that Integer
takes less memory. It's also kind of self documenting about the size of the
#.

With memory gigs now about the size of a thumbnail, what are the major
pro's and cons of still using As Integer versus As Long.

Thanks.
--
Neal Z