A question of concept/logic

  • Thread starter Thread starter The Dude
  • Start date Start date
T

The Dude

Hello folks,

I would really appreciate your help on the programming logic of the
following example:

Let's say you have an invitees table with Invitees_ID and Invitees_Names
Assuming that you have another table this time with Events_ID and _Name.

Now I would like to be able to select invitees, some of them, and invite
them to q selected event.
Which logic should I use:
- Make a third table with gathered Invitees_ID and Events_ID?
- Make a table for each events' year so that it can last in the future?

Any correction/info will be greatly appreciated :)

Have a nice day

P.S. sorry about the other post in the forms section...
 
You would make a third table with, for example, EventID and InviteeID fields
as a compund primary key, plus any other fields - like EventDate - that are
specific to each particular event
 
- Make a third table with gathered Invitees_ID and Events_ID?

Junction or many-to-many table...standard practice

--

Kevin3NF
SQL Server dude

You want fries with that?
http://kevin3nf.blogspot.com/

I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

A question of concept/logic 5
A matter of junction table and its functions 3
combo box in subform? 4
Design ideas for a user controlled invitation list 1
Outlook Calendar sends unreadable attachment when inviting attende 11
Sending a meeting invitation with multiple timeslots 1
Logic for WHERE statement in a combo box? 5
calculate time to complete application 8

Back
Top