Jonathan Duncan wrote:
> 1 1/16"
> 3/8"
> 3/16"
> 1 5/32"
> 45º
> 10º
> 2 7/16"
>
> These aren't pretty numbers to enter into a database. The simple way would
> be to enter them as CHAR's and forget about them, but then searching on that
> could cause problems.
If you're not going to be doing a
Thanks everyone, you have given me some ideas. Jonathan
Steve Edberg <[EMAIL PROTECTED]> said:
> Well, as far as the inches and fractions thereof go, you could always
> normalize your data to the smallest measurement - for example: if the
> smallest increment is 1/32 of an inch, store all me
Well, as far as the inches and fractions thereof go, you could always
normalize your data to the smallest measurement - for example: if the
smallest increment is 1/32 of an inch, store all measurements in terms of
32nds. So, 1" => 32, 1-5/32" => 37, and so on. Then you could store the
values i
I am creating a database for a website that sells tools. Unfortunately they
aren't measured in metric. Most of the measurements look something like:
1 1/16"
3/8"
3/16"
1 5/32"
45º
10º
2 7/16"
These aren't pretty numbers to enter into a database. The simple way would
be to enter them as CHAR's
