Table `member`
// already exists
// column userid will be foreign key referred to below in `member_custom_field_response`

Table `member_custom_field`
field_id int auto_increment primary key
priority int
name varchar
description varchar
field_type ( text, password, textarea, checkbox, radio, select ) // Enum tends to lend itself to the complexity of this column, but I know we're avoid those ... suggestions or are people cool with using an enum for this? I don't see how a single char can represent this and be meaningful. And a multichar would be more space-consuming than an enum. This column will also not need to change any - those are the only types of form fields that exist in HTML right now and probably for a long while.
b_select_multiple smallint // for checkbox, select
b_required smallint
b_visible_signup smallint
b_visible_profile smallint

Table `member_custom_field_option`
field_id int // foreign key shared primary key
option_id int // sequential 1-n per field shared primary key
value varchar

Table `member_custom_field_response`
user_id int // foreign key shared primary key
field_id int // foreign key shared primary key
option_id int // foreign key shared primary key
value varchar // static value of answer provided then

Questions:
1) Should we offer a seventh field type "richeditor" that utilizes the FCK editor? Not sure of uses and sounds messy, but I thought it was worth mentioning.
2) Do you see any columns in those tables that are missing?
3) Are you cool with the table names / can you think of better ones?