By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,398 Members | 944 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,398 IT Pros & Developers. It's quick & easy.

general db design

P: n/a
I'm creating a database to replace an equipment request form for field
workers out of my office. One of the items on the form is "Tent (note
type and # needed)". The person filling out the form has a 2.5 inch
long line to enter this info. In the database, should that be broken
into one field for the type of tent and another for the number of
tents? Seems like overkill to do that since our office tops only
about 40 people. There are numerous similar examples on this form.

Doug
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
rkc

"Wilder" <Do*********@nps.gov> wrote in message
news:b2**************************@posting.google.c om...
I'm creating a database to replace an equipment request form for field
workers out of my office. One of the items on the form is "Tent (note
type and # needed)". The person filling out the form has a 2.5 inch
long line to enter this info. In the database, should that be broken
into one field for the type of tent and another for the number of
tents?


Yes. Different types of information should be stored separately.

How would you query for the number of 2 person Mountain tents
requested if the data was stored in a single field as

2 person Mountain tent 6
7 2 person Mountain tents


Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.