Structure it as a TEXT field. The only reason to set up a field as any kind
of number is if you expect to do some kind of mathematical operation on it.
If you are not, then it is not really a number, it just LOOKS like one.
Failure to understand the difference is a common mistake that database
designers make. I do a lot of work in the Medical field and one of the
biggest problems I see is that databases are often designed so that Medical
record "numbers", and another "number" called a DRG are often structured as
numeric types. There are times with these and other "numbers" that are used
only as identifiers require the leading zeros, or some sorting algorhythm
where the position of each digit is important. I don't see anyway to store
an IP address as a number anyway. It COULD be stored in four separate
numberic fields, but why bother?
The only exception to this is when a process has to generate the id number
based on a sequence of some kind, but then it should usually be converted to
a string for subsequent use.
----- Original Message -----
From: "Michael Thomas" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Saturday, December 02, 2000 4:04 AM
Subject: IP Logging DB Data Type???
> I have a quick question about IP logging. I want to log an IP address into
a
> database but Im not sure which is the correct data type to use. Will Float
> do it or Double Precision???
>
> BTW Im going to have to do this for MS Access & SQL Server 7.0 so I'll
need
> the correct data type for each one. Im using MS Access 97 for testing
> purposes but the live database will be an SQL Server 7.0 DB.
>
> TIA,
> Mike
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
