and "Not Applicable" a value and record in the fruit lookup table.
-Cameron
-----------------
Cameron Childress
Sumo Consulting Inc
---
land: 858.509.3098
cell: 678.637.5072
aim: cameroncf
email: [EMAIL PROTECTED]
-----Original Message-----
From: Jamie Jackson [mailto:[EMAIL PROTECTED]
Sent: Monday, February 09, 2004 10:55 AM
To: CF-Talk
Subject: Select Field Values
Here's a rudimentary little question, but one that I go back and forth
on:
Say you have a dynamically driven select box:
What's your favorite fruit? [select name = "fruit"]
-Apples [value = 1]
-Oranges [value = 2]
-Other
-Not Applicable [value = NULL]
(Feel free to take issue with any of the following:)
I'd assign the "Not Applicable" option a value of NULL in the DB
field, so it would have neither a foreign key nor lookup value.
However...
1. Generally, should the "other" option be in the database (as a field
in the lookup table)?
2. Or alternatively, should the "other" option be a static one (if so,
how is it best represented in the DB)?
Thanks,
Jamie
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
