List or combo box q. Can't see the forest through the trees!

[jeff]

Hi, i'm working with Micro Access 2002 on Win Vista

Trying to accomplish the following, but can't see how to get there.
Looking to use a list or combo box to accomplish the following:

i have a list of workshops people attend. Two columns to key from.
Column-1: Date Column-2: Description
example:
11/1/09 workshop-1
11/15/09 workshop-2
12/1/09 workshop-3
12/30/09 workshop-4
etc.

i want to have access read the values that i put into a list somewhere,
then have a dropdown list on peoples form page that allows me to multiple
choice which workshops they have attended and store those selected items in
another field.
The dropdown only needs to offer up the date of the workshop only, not the
description. But, both columns would need to be stored, together or
seperately, in their final spot.

Basically, i want to be able to select the date they went to the workshop
when i input it in. And be able to view the workshops that they have
attended in another area.

I'm sure this can be done, but can't stumble on the correct function or
combinations of things to do to get it to happen.

I have already tried the basic list and combo boxes, but it is not that
straight forward i see. I can get the columns originally set up to choose
from, but it won't allow me to make multiple choice options or to store
multiple entries. I don't have the correct thought pattern yet. On board
help or knowledge base no help at this point!! Any additional help
appreciated.
Thanks, in advance,
j

 

[Lynn Trapp]

Jeff,
Can you describe your database structure for us? What are the table names
and fields?

 

[jeff]

I have one table with all my fields, queries, forms, reports, etc in that.
On the primary Profile Form (name and other general info) i want to add a
list or combo box that allows me to make single or multiple choice selections
(for workshops they attend, I'll key off the date) and have it store that
info in another field or fields called "workshop date" and/or "workshop
descr".
This way i can pull up each persons profile one at a time and select the
workshop(s) that they attended.
I will also be able to view this info by putting the stored date field up on
thier profile form page.
If that makes sense.
Thanks,

 

[John W. Vinson]

I have one table with all my fields, queries, forms, reports, etc in that.

Well... no. You don't.

A Database contains Tables, Forms, Reports, Queries, Modules and Macros. These
are all different kinds of objects. A Table will not "contain" forms or
reports.

If all of your data is stored in one table, you're using a spreadsheet, not a
relational database. You should have one table for eack kind of "entity" -
real-life person, thing or event. A workshop is one kind of entity; a person
is a different kind of entity; the event of a person attending a workshop is
yet a third kind of entity. You need at LEAST three tables.

On the primary Profile Form (name and other general info) i want to add a
list or combo box that allows me to make single or multiple choice selections
(for workshops they attend, I'll key off the date) and have it store that
info in another field or fields called "workshop date" and/or "workshop
descr".
This way i can pull up each persons profile one at a time and select the
workshop(s) that they attended.
I will also be able to view this info by putting the stored date field up on
thier profile form page.

All very easy with properly designed tables; nightmarishly difficult if you in
fact have only one table.

 

[jeff]

Hi guys, and thanks for the reply's.
I'm not exactly an Access Administrator, but i did think i was on the wright
track when i put together my database.
But, after reading your response, i gather i may not have set it up quite
right.
The way i have it all set up i can get all the reports and queries, forms,
etc that i need so far. I can think about a restructure, but that would have
to be later on.
This isn't a big deal for my, but i thought i set it up correct. i've been
useing it this way for several year now. i guess i'm getting to the point
were proper structure matters. maybe i'll hit the Access for Dummies in my
spare.
Thanks for your time.
I'll see what i can do from here.