[AccessD] 16 bit Integer bad practice

I agree. What should be the yardstick for determining good vs bad
programming practices? Efficiency? avoiding legacy functions/data types that
may be eliminated in future releases? Readability of the code so others can
maintain it? Robustness of the code (whatever that means)? Certainly some so
called "bad" practices are not all black and white. I will say, however,
there are many practices it is best for new and even intermediate
programmers to avoid until they master their craft. Walk before running,
paint by the numbers before attempting to be Picasso, etc. While I now
understand the uses and abuses of globals, I'm also very glad I was warned
off them when starting out. I shutter to think how many fingers I would have
lost playing with that particular power tool before I was ready.
Jim Hale


-----Original Message-----
From: Scott Marcus [mailto:marcus at tsstech.com]
Sent: Wednesday, May 18, 2005 12:49 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] 16 bit Integer bad practice


Drew,

Less efficient because they are 16 bit does not make them bad practice.
It makes them slower.

Let's take this to an extreme, should I set up a long and pack all my
Booleans into that so that they take up less space (efficient)?
Certainly Not. 

You have gone off the deep end.


***********************************************************************
The information transmitted is intended solely for the individual or
entity to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or
other use of or taking action in reliance upon this information by
persons or entities other than the intended recipient is prohibited.
If you have received this email in error please contact the sender and
delete the material from any computer. As a recipient of this email,
you are responsible for screening its contents and the contents of any
attachments for the presence of viruses. No liability is accepted for
any damages caused by any virus transmitted by this email.