> should I put three values into one column?
You probably don't want to do this because then your data would violate
first normal form and make the table a PITA to query. An appropriate
database design technique would be to store the values in a separate table
with a one-to-many relationship.
The example schema below allows a department to have multiple department
types. The application would insert a Department row and then one row into
Departments_DepartmentTypes for each selected DeparmentType.
CREATE TABLE DepartmentTypes
(
depttype varchar(10) NOT NULL
CONSTRAINT PK_DepartmentTypes PRIMARY KEY
)
CREATE TABLE Departments
(
deptcode varchar(10) NOT NULL
CONSTRAINT PK_Departments PRIMARY KEY
)
CREATE TABLE Departments_DepartmentTypes
(
deptcode varchar(10) NOT NULL,
depttype varchar(10) NOT NULL,
CONSTRAINT PK_Departments_DepartmentTypes
PRIMARY KEY(deptcode, depttype)
)
--
Hope this helps.
Dan Guzman
SQL Server MVP
"reneeccc west" <re**********@hotmail.com> wrote in message
news:40*********************@news.frii.net...
Let's say, the column name of the drop down box is "depttype" and it has
three values because it is allowed to choose more than one value. should
I put three values into one column?
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
