I am setting up a database for a research project. I would like to enter the
data within the table as it is easier to see everything together.

I have a combo box for General Injury Region, which is upper extremity,
lower extremity, spine. I would like to the second combo box populate based
on the first with shoulder, hand, wrist, etc.

Thanks in advance!

Debi wrote:

> I am setting up a database for a research project. I would like to enter
> the data within the table as it is easier to see everything together.
>
> I have a combo box for General Injury Region, which is upper extremity,
> lower extremity, spine. I would like to the second combo box populate
> based on the first with shoulder, hand, wrist, etc.
>
> Thanks in advance!

No, Use a form.

Warning: your first paragraph makes it sound as if you're thinking in
spreadsheet idiom. Databases are different, and in many ways much more
powerful. The key is understanding how to structure your data, and it's
vital to get that right first. Here are a few links to get you started:

Free samples from Lynda.com on table design:
http://www.lynda.com/home/Player.aspx?lpk4=31001 (A2007)
http://www.lynda.com/home/Player.aspx?lpk4=13150 (A2003)

Microsoft tutorial on table design:
http://bit.ly/ms-access-tables-tutorial

You can also find video tutorials on many Access topics (e.g. Combo Box) by
Googling.

Back to the question!. Don't be tempted to use "Lookup Fields" in tables -
there are lots of reasons why experienced Access users never use these. The
typical scenario is to divide your data between a number of tables which
represent distinct "entities" in the world you are modelling. These
entities will be related (e.g. one-to-many, many-to-many) and a record in
one table may include a reference (a "foreign key") to a record in another
to represent these relationships. When data needs to be extracted
selectively or in a particular sort order, queries are used to draw together
related records. Forms (or reports) can be based on these queries. It's
common to have several forms based on the same data tables to support
different uses of the data.

Once you have a suitable query on which to base a form, try using the Form
Wizard. In Access 2007 it's particularly easy - highlight the query which
will form the "Record Source" of your new form, and, in the Create tab,
simply click the Form button (left-most in its group). Bingo - a basic form
for your data. To change one of the text boxes (default) into a combo box,
simply right-click it and pick "Change to..." and pick combo box. You'll
then adjust the combo box's properties appropriately (always Row Source, and
often Number of Columns and Column Widths). It's surprisingly quick and
easy after the first time.

Finally, this article deals with the particular issue you ask about:

http://office.microsoft.com/en-gb/ac...CL100570041033

HTH

Phil, London

"Debi" <(E-Mail Removed)> wrote in message
news:677CC359-67C4-41D5-A771-(E-Mail Removed)...
> I am setting up a database for a research project. I would like to enter
> the
> data within the table as it is easier to see everything together.
>
> I have a combo box for General Injury Region, which is upper extremity,
> lower extremity, spine. I would like to the second combo box populate
> based
> on the first with shoulder, hand, wrist, etc.
>
> Thanks in advance!

Here's a neat video I found on this!

http://www.youtube.com/watch?v=pMiJHhjzC8Y

Phil

"Philip Herlihy" <(E-Mail Removed)> wrote in message
news:O752Hv$(E-Mail Removed)...
> Warning: your first paragraph makes it sound as if you're thinking in
> spreadsheet idiom. Databases are different, and in many ways much more
> powerful. The key is understanding how to structure your data, and it's
> vital to get that right first. Here are a few links to get you started:
>
> Free samples from Lynda.com on table design:
> http://www.lynda.com/home/Player.aspx?lpk4=31001 (A2007)
> http://www.lynda.com/home/Player.aspx?lpk4=13150 (A2003)
>
> Microsoft tutorial on table design:
> http://bit.ly/ms-access-tables-tutorial
>
> You can also find video tutorials on many Access topics (e.g. Combo Box)
> by Googling.
>
> Back to the question!. Don't be tempted to use "Lookup Fields" in
> tables - there are lots of reasons why experienced Access users never use
> these. The typical scenario is to divide your data between a number of
> tables which represent distinct "entities" in the world you are modelling.
> These entities will be related (e.g. one-to-many, many-to-many) and a
> record in one table may include a reference (a "foreign key") to a record
> in another to represent these relationships. When data needs to be
> extracted selectively or in a particular sort order, queries are used to
> draw together related records. Forms (or reports) can be based on these
> queries. It's common to have several forms based on the same data tables
> to support different uses of the data.
>
> Once you have a suitable query on which to base a form, try using the Form
> Wizard. In Access 2007 it's particularly easy - highlight the query which
> will form the "Record Source" of your new form, and, in the Create tab,
> simply click the Form button (left-most in its group). Bingo - a basic
> form for your data. To change one of the text boxes (default) into a
> combo box, simply right-click it and pick "Change to..." and pick combo
> box. You'll then adjust the combo box's properties appropriately (always
> Row Source, and often Number of Columns and Column Widths). It's
> surprisingly quick and easy after the first time.
>
> Finally, this article deals with the particular issue you ask about:
>
> http://office.microsoft.com/en-gb/ac...CL100570041033
>
> HTH
>
> Phil, London
>
> "Debi" <(E-Mail Removed)> wrote in message
> news:677CC359-67C4-41D5-A771-(E-Mail Removed)...
>> I am setting up a database for a research project. I would like to enter
>> the
>> data within the table as it is easier to see everything together.
>>
>> I have a combo box for General Injury Region, which is upper extremity,
>> lower extremity, spine. I would like to the second combo box populate
>> based
>> on the first with shoulder, hand, wrist, etc.
>>
>> Thanks in advance!
>

I've learned not to ignore anything you say, but I don't get that. To fail
3NF, one table would have to have a field whose value was not tied to the
key - can't see it! In the State table, the key is the (only) value - but I
don't think that makes a difference?

One of the benefits of offering answers here is that you get corrected from
time to time!

Phil

"KenSheridan via AccessMonster.com" <u51882@uwe> wrote in message
news:a088e3d5c4288@uwe...
> Apart from the fact that his table is not normalized to Third Normal Form!
>
> Ken Sheridan
> Stafford, England
>
> Philip Herlihy wrote:
>>Here's a neat video I found on this!
>>
>>http://www.youtube.com/watch?v=pMiJHhjzC8Y
>>
>>Phil
>>
>>> Warning: your first paragraph makes it sound as if you're thinking in
>>> spreadsheet idiom. Databases are different, and in many ways much more
>>[quoted text clipped - 51 lines]
>>>>
>>>> Thanks in advance!
>
> --
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/For...arted/200912/1
>