[AccessD] Data Types (was - Global Variable)

Hmmmmm....good point.  However, and I'm just playing devil's advocate...if a
Long Integer is going to get a value too big to put into a 'foriegn' system,
wouldn't there be a problem with the design of the foriegn system (if that
is a true value..something that should be stored)?  Know what I mean?

Drew

-----Original Message-----
From: John Bartow [mailto:john at winhaven.net]
Sent: Wednesday, May 18, 2005 10:38 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Data Types (was - Global Variable)


I've considered no longer using Integers for variables because of the 16 bit
issue. 

However, I have been reluctant to do so for field datatypes. When utilizing
data from another non-access application this may affect how the other apps
behave. Comments?

John


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Wednesday, May 18, 2005 10:24 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Global Variable

 However, Integers, while they may be misused, even if they are used
correctly, they are still bad practice, because they are 16 bit variables.  

========Why is that bad? If it saves you the trouble of writing code that
does exactly what the data type does -- reject an inappropriate value? Why
would you bother? What is bad about using the data type for its said
purpose, regardless of its size?

Susan H. 

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com