On 4/12/00, Ken M. Mevand penned:
>i prefer method (a) for this reason : there is no need for the CF templates
>to interprete the meaning of the values. however, it seems quite silly to
>have a table with 3 rows on data only. but there are also advantage of
>future expansion. but what about gender which has only 2 possible value (at
>least in the foreseeable future).
'A' for sure.
A table, Membership_Types with an indexed column of
Membership_Type_ID and a column of Membership_Type naming the type.
Relate Membership_Type_ID in that table to Membership_Type_ID in the
members (I presume) table. Populate the select menu (or whatever) for
choosing a membership type with the data from the Membership_Types
table. You can add more membership types later and the menu will be
populated automatically. If you change the name of a membership type,
no updating to do in the members table.
Gender could be a simple yes/no field. Bit [?] for SQL Server? Make
it Male. If it's 1, he's a male, if not, she's a female.
Bud Schneehagen - Tropical Web Creations
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
ColdFusion Solutions / eCommerce Development
[EMAIL PROTECTED]
http://www.twcreations.com/
954.721.3452
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
