Recent content by John O'Malvern

Agreed. I'm working on it. I'll post here if I get stuck again. Thanks all

Same thing happened. I should have said it is a form with a subform (which shows CategoryTypes). But I see the problem, the Wizard created the main form on SQL it created, selecting fields from the Contacts table that were in my query* , which is using data from four tables: .......(*without...

My query lists 108 current members, but when I base a form on it [I used the Wizard, without making any design changes] it lists all 400+ members, including those who have left. Why? Surely the form should only show the records in the query's datasheet view?

Thanks. I hadn't noticed that button. (Writes Mr Unobservant.)

Just to confirm, the problem in the original post has been resolved. thank you all.

Sorry, earlier, when I said (referring to your earlier question about what is a contact category): Problem solved, but it means the type of member - Associate [=as yet unqualified], Member, Friend, Honorary etc (I inherited it, and some terms still confuse me after 2 years! :( ) I was...

I've not heard the term 'many to many table' before. It was created in order to resolve [ie prevent the existence of] a many to many relationship, which I've always understood to break the rules of a relational database.

Problem solved, but it means the type of member - Associate [=as yet unqualified], Member, Friend, Honorary etc (I inherited it, and some terms still confuse me after 2 years! :( )

Thanks, I built a new query from scratch, and it now works. (Do you mean that possibly it cannot be used as an Update query?)

A form to enter a new member's details has stopped working, after adding an intermediate table. Previously: now: (the red squiggles mark fields I know are not needed) the tblContact_Categories was needed between Contacts and tblCategoryTypes as one contact can have more than one CategoryType...

No, for GDPR reasons. :(

AFK for a few hours, now. Thanks for all suggestions.

ContactID is the primary key of the table Contacts ! (Which is the main table of the database)

Youi're right - CategoryType shouldn't be in tblContact_Categories. (the ID is superfluous, also) Just the two FKs which together form a primary key, of course. My reasoning for having both tables is as stated in my reply to plog

Thank you! I'll give that a go when I get a chance. Re. Notes 1 Yes, I know not to use spaces, I inherited a big, elaborate database in current use, adn don't have the time & energy to put all those things right. :( 2 I realise now that Category Type in tblContact_Categories is superfluous...