[AccessD] Event Invites

Self joins have to point from child back to parent.  IOW there must be a parent ID (InvitedBYID in 
this case).  Any "invite" in this case can of course only be a guest (or invite) of a single other 
person.  Other than that it works.

The biggest issue is flattening it out, particularly if you have to have the entire path back to the 
original parent who has no other parent.

If "who invited me" is all that matters, then it is trivial, if the InvitedBy field contains 
anything other than zero then a name is pulled and displayed / printed (Outer join).

Of course if a guest invited guests, and that guest is deleted then you have orphaned invites.  You 
definitely should handle that in some manner.  The OnDelete event would work well.  ;)

John W. Colby
www.ColbyConsulting.com


Charlotte Foust wrote:
> Self joins get messy if you delete a guest.  And can an additional guest
> invite someone, or only the main guest?  A join table gives you more
> flexibility at the cost of some maintenance.
> 
> Charlotte Foust 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
> Sent: Tuesday, August 11, 2009 9:34 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Event Invites
> 
> Select the main guest in combo 2 and then view a list of names from
> which the user can select one or more partners.
> 
> =======If they're all in the same table to begin with and if each
> additional guest can have only one main guest, can you use a self-join
> -- add a field that contains the main guest's PK? Populate from the
> self-join field???
> 
> Susan H.
> 
>