Dual Listbox

[Tom]

Experts,

I need some help with modifying a db that contains a dual listbox. More
specifically, I have the following:

Tables:
- [00_tblMeetingsLookup]
- [00_tblMembersLookup]
- [tblMeetingAssignments]

Table [tblMeetingAssignments] acts as a junction table between the 2 other
tables.

Now, currently, I have a single form (frmMeetings) that contains 2 listboxes
("Currently Available Members" and "Currently Assigned Members").
Essentially, it allows me to "move" members from one list box (Available) to
another listbox (Assigned).

Thus far, this works great. Well, let me step just a bit... I copied this
process from "Teams and Team Members". Meaning, a "unique team" can have
one or many members.

For instance,
Team A can have members 1, 2, 4, 7
Team B can have members 1, 3, 5, 7

.... the important point is that there's only one "Team A" and one "Team B".

Now... the transition... I replicated this process and can have the
following:
Meeting A can have members 1, 2, 4, 7
Meeting A can have members 1, 3, 5, 7

However, "Meeting A" can be held today, next week, next month, and so on.
So, I have multiple instances of the same meeting. So, the following could
be the case:
Meeting A were attended by members 1, 2, 4, 7 on 01-16-2006
Meeting A were attended by members 1, 2, 3, 4, 6, 7 on 01-23-2006
Meeting A were attended by members 3, 4, 7 on 02-16-2006
.... and so on

I'm not sure how to integrate this "additional child" (date) in the current
process.

Since "pictures" can be worth a thousand words, I have uploaded a sample
file (DualListbox.zip) to: http://www.savefile.com/files.php?fid=4631017


Again, how would I go about adding the Date field into this table structure
and form so that I can have an unlimited number of dates for each meeting?

Thanks,
Tom

 

[mscertified]

A meeting is a single entity so obviously has to be on a single date. So you
cant have meeting A on two different dates.
The date has to be part of the meeting primary key.
A, B, C etc. could be meeting type.
You could then assign people to meeting type (if you wanted) or to
individual meeting depending on your requirements.

-Dorian

 

[Jeff Boyce]

Perhaps the word "meeting" has different meanings...

A monthly user group meeting could be considered one meeting, with many
instances (this month's meeting, next month's meeting, the meeting held
during January of '05, etc.).

If any of the meetings can happen more than once (see above example), a
junction table needs to hold:

trelMeetingInstance
MeetingInstanceID (a primary key)
MeetingID (i.e., the user group meeting general title)
MeetingDate (i.e., the instance)
... (and any other details re: this instance...)

Then the meeting attendees list shows up as:

trelMeetingAttendee
MeetingAttendeeID (a primary key, in case you don't use the multi-column
key)
MeetingInstanceID (which instance)
AttendeeID (who attended)

Regards

Jeff Boyce
<Office/Access MVP>

A meeting is a single entity so obviously has to be on a single date. So
you
cant have meeting A on two different dates.
The date has to be part of the meeting primary key.
A, B, C etc. could be meeting type.
You could then assign people to meeting type (if you wanted) or to
individual meeting depending on your requirements.

-Dorian

Experts,

I need some help with modifying a db that contains a dual listbox. More
specifically, I have the following:

Tables:
- [00_tblMeetingsLookup]
- [00_tblMembersLookup]
- [tblMeetingAssignments]

Table [tblMeetingAssignments] acts as a junction table between the 2
other
tables.

Now, currently, I have a single form (frmMeetings) that contains 2
listboxes
("Currently Available Members" and "Currently Assigned Members").
Essentially, it allows me to "move" members from one list box (Available)
to
another listbox (Assigned).

Thus far, this works great. Well, let me step just a bit... I copied
this
process from "Teams and Team Members". Meaning, a "unique team" can have
one or many members.

For instance,
Team A can have members 1, 2, 4, 7
Team B can have members 1, 3, 5, 7

.... the important point is that there's only one "Team A" and one "Team
B".

Now... the transition... I replicated this process and can have the
following:
Meeting A can have members 1, 2, 4, 7
Meeting A can have members 1, 3, 5, 7

However, "Meeting A" can be held today, next week, next month, and so on.
So, I have multiple instances of the same meeting. So, the following
could
be the case:
Meeting A were attended by members 1, 2, 4, 7 on 01-16-2006
Meeting A were attended by members 1, 2, 3, 4, 6, 7 on 01-23-2006
Meeting A were attended by members 3, 4, 7 on 02-16-2006
.... and so on

I'm not sure how to integrate this "additional child" (date) in the
current
process.

Since "pictures" can be worth a thousand words, I have uploaded a sample
file (DualListbox.zip) to: http://www.savefile.com/files.php?fid=4631017


Again, how would I go about adding the Date field into this table
structure
and form so that I can have an unlimited number of dates for each
meeting?

Thanks,
Tom