[AccessD] Re: design/development question on representing mtm relationships

I do not use "AutoAdd" either.  Did not think
I even mentioned it.
I always open a form because of the other
constraints against lookup tables.

At 12:00 PM 01/07/2004 -0500, you wrote:
>Date: Thu, 01 Jul 2004 22:09:54 +1000
>From: "Stuart McLachlan" <stuart at lexacorp.com.pg>
>Subject: Re: [AccessD] RE: design/development question on representing
>         mtm     relationships
>To: Access Developers discussion and problem    solving
>         <accessd at databaseadvisors.com>
>Message-ID: <40E48BB2.25038.84DD5BE at localhost>
>Content-Type: text/plain; charset=US-ASCII
>
>On 1 Jul 2004 at 6:42, Robert L. Stewart wrote:
>
> > Susan,
> >
> > Ok, I see what you mean.  And here is how I handle such things.  There are
> > two methods.  All of the "lookup" type data, in your example, the
> > publisher, would be a drop down list in a combobox.  So, you would either
> > use the not in list event to be able to add it, or a button to the 
> right of
> > the combobox labeled "Add" that would open a data entry form to do the
> > add.  I have done it both ways.  And, there are pros and cons for doing it
> > both ways.  The biggest con for the not in list event is that it makes it
> > too easy for people to enter things with an incorrect spelling.
>
>I never use  "autoadd" in the NotInList.  The NotInList event triggers a 
>msgbox
>to confirm whether they want to add a new record  If they confirm, I open a
>modal Data Entry form with the entered data already filled in for the user to
>complete/confirm.