On 17/2/08 21:27, "Chuck Pelto" <[EMAIL PROTECTED]> wrote:

> I'm working on a system to rapidly enter events that attendees at a
> convention want to participate in.
> 
> These various EVENTS are in a table, separate from the table of
> ATTENDEES.
> 
> There is a field in the ATTENDEES that is established as a CheckBox
> field in which all the possible events from the EVENTS table are listed.
> 
> The idea is that the person entering data on which events an attendee
> is registering for will be checked in that CheckBox field.
> 
> I'd prefer that the events are listed in that field in chronological
> order. The EVENTS table has a field for that, with each record of
> each event.
> 
> The only way I seem to be able to get the events to sort out
> properly, i.e., in chronological order, is to include the DateTime
> field for events in the Value List; as the second field.
> 
> I'd rather not show the DateTime data in the CheckBox field. But if
> that data is not selected in the ValueList set up, the events will
> not sort properly. This, despite setting the Table for this
> relationship, between EVENTS and ATTENDEES to sort based on (1)
> DateTime and (2) Title of event.
> 
> How do I accomplish this?

Chuck

I think I'd approach this very differently.

I'd display the available events in a portal. That way you can sort them in
any way you like.

A button on each portal row would move that event into the attendees
'shopping cart' of registered events. I'd make the shopping cart another
portal to an attendee-event join table.

If you want to be clever, you could arrange things so that an event that has
been registered does not appear in that person's list of available events.

I think this scheme has a number of advantages. First, you can sort and
display your list of events in any way you like. Second, you get a proper
related table of attendee-event records (which you may think you don't need
now, but you may be pleased to have it as the solution develops). Third, you
build in greater future flexibility -- it will be easy for example to limit
the events available to an attendee depending on the days they have signed
up for or their qualifications or whatever.

As I say, that would be my approach. I feel that by getting all the event
names into a single text field (that's what check boxes do) you are digging
bit of a hole for yourself. It may never be important, but if the solutions
grows it will be.

Steve

Reply via email to