Martin Reid
mwp.reid at qub.ac.uk
Tue Aug 11 12:36:21 CDT 2009
Each main guest can invite one or more additional guests. The additional guest cannot invite. As JC says the issue now is creating a flat record for the merge. Used another table and a multi select list box. But it is a two stage process at the moment. You invite one or more main guests. In response to prompt you can then select for each main guest one or more additional guests. This is then written to a table which details the main guest ID , the event ID and the ID of each additional guest. What I have is a guest table which once the data is input gives me M Reid Guest 1 Event2 M Reid Guest 2 Event2 M Reid Guest 3, Event2 OH all unbound of course (<: Martin Martin WP Reid Information Services The Library at Queen's Tel : 02890976174 Email : mwp.reid at qub.ac.uk ________________________________________ From: accessd-bounces at databaseadvisors.com [accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby [jwcolby at colbyconsulting.com] Sent: 11 August 2009 18:05 To: Access Developers discussion and problem solving Subject: Re: [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