Thanks for helping me out on this.... Something must be wrong with me
today... I can't get this to work correctly.
I've removed the 'autonumber' field and set a primary key on the two fields
that will append in the tblMailingListLink - ContactID and ListID. ListID is
a constant? Could that be an issue? The relationships and query have not
changed. What else could be left?
> The new field, the auto number, can't be use to remove the duplicates.
> You have to decide which fields you don't want to repeat, and declare the
[quoted text clipped - 33 lines]
> > > >
> > > > Thanks for reading!
In the append query, change the syntax to
Insert Into TableName (Field1, Field2)
Select Distinct Field1, Field2 From TableName
In the select part add distinct
Or, open the query in design view, open the properties, and change the
Unique values property to Yes, it will add the distict for you

Signature
I hope that helped
Good Luck
> Thanks for helping me out on this.... Something must be wrong with me
> today... I can't get this to work correctly.
[quoted text clipped - 41 lines]
> > > > >
> > > > > Thanks for reading!
Build or Die - 16 Nov 2005 21:29 GMT
Just when I thought that was going to do it - not there yet.
My new syntax:
INSERT INTO tblMailingListLink ( ContactID, ListID )
SELECT DISTINCT tblContacts.ContactID, forms!frmmailinglist.listselect AS
ListID
FROM tblContacts
WHERE (((tblContacts.RemoveFromList)=No));
It seems like this should resolve any query problems. Would having 'enforce
referential integrity' set on in the relationships be a problem?
Got anymore tips for the guy who can't get an append query to work on a many
to many relationship?
Thanks for all your help.
> In the append query, change the syntax to
>
[quoted text clipped - 51 lines]
> > > > > >
> > > > > > Thanks for reading!