Again, Thank you for the training and help.  Im trying to do a database for my Freemason Lodge.  Ive got part one and two working.  A members Database and an account database, they seem to be working well.  But the third section, a Journal of events cant get off the ground.
I am beginning to think Im conceptually looking at the structure incorrectly.  I have a present paper system that needs to be followed as closely as possible.
It starts with an Event in a ledger.  The event records minimum information about what the lodge did at one meeting.
The sub Table design effort starts with what we call a summons, a document that indicated to all members the next months scheduled events, a rehearsal, a business meeting and the regular meeting, along with any special events scheduled.
In integral field in both the Event Table and all Sub tables is a Document Number which Has a concatenated (Prefix Sum-, indicating what was the event type and a date code, yymmdd).  This needs to be recorded in a Journal.  After that is done.  A special event Summons needs to be detailed and a report generated.  Other different event types need to be recorded in the Event table, Journal also. Those other types will have different fields then the summons and are recorded in Sub tables named for the meeting types.
Originally, I did a one to many relationship between the event table and sub-tables.  But when I called the form for the sub table I got all events types not just the summons.  Then I tried a one to one relationship and then when I looked at the event table I only got the ones connected to Summons.  When looking at the event table I need to see all types of event records.
I could use a query to select Summons Type records but that made updating certain fields from Event table to Summons like the Document Number not load.
Should I reverse the process and do the special Tables first and transfer to the event table as a one to many or is that a many to one?