I noticed that nobody answered.

On your later question, I think that you are making the mistake of mostly
skipping over step 1 and step 2:

Step 1 Clearly decribe the database-relevant aspects of the real world
process that you want to database, and the mission that you want your
database to accomplish. Especially decide what the entities are that you
want to database, and what the relationships are between them. Decide what
types of “one to one” information/attributes you want to store/record for
each entity. If you run across a “many to one” situation, (like many phone
numbers for each company) consider that to be an entity. Do all of this
without using any Access terminology. If you need structural help (as I
think you do) describe what you came up with under step 1 in your post.

Step 2 Design a good table structure which will accomplish databasing your
process and support accomplishment of your mission. Generally, each entity
will get a table, and each one-to-one type piece of information about that
entity will get a field in that table.

Step 3 Design queries, forms, reports etc. to accomplish your mission.

Hope that helps a little.