Access Shared Date between tables, plus

[Guest]

I have a master table with a list of people. These people register for our
different events. I need to create another table/form/query (not sure what
it's officially called) which will carry over only a specific group of people
(like a query) signed up for each event (some overlap). However, I need to
have additional fields in this new ‘table’ with more information not included
in the master table.

Most importantly, I need them LINKED. If a new registrant signs up I want to
be able to click a box on the main table and have the change show up on the
sub "table" (much like a query). But my make-table queries won’t allow me to
add field not in the main table.

Is such a thing even possible on Access? Can anyone please help me? What is
the best route to take?

 

[Jeff Boyce]

Nancy

It sounds like you are saying you want to keep "registration" information
(say, like which students signed up for which classes?).

You have people, you have events, and you have registrations. You need
three tables to do this in Access.

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[John Vinson]

I have a master table with a list of people. These people register for our
different events. I need to create another table/form/query (not sure what
it's officially called) which will carry over only a specific group of people
(like a query) signed up for each event (some overlap). However, I need to
have additional fields in this new ‘table’ with more information not included
in the master table.

Most importantly, I need them LINKED. If a new registrant signs up I want to
be able to click a box on the main table and have the change show up on the
sub "table" (much like a query). But my make-table queries won’t allow me to
add field not in the main table.

Is such a thing even possible on Access? Can anyone please help me? What is
the best route to take?

You'ld need a registration table with a PersonID field - a link to the
Primary Key field of your master list. The registration table should
not have any information about the person (other than this link field)
- you'ld just create a Query linking them.

If this is a list of people registered for an event, you'll also want
an Events table, and an EventID field in the registration table.

If you're assuming that you must make a new table for every event, or
for every registration - you don't. Reports can and should be based on
Queries joining multiple tables.

John W. Vinson[MVP]