Problem w/ Child Tables Auto Serializing

[rexkwilliams]

I am sorry for having to ask, but I did try to help myself first, but I am not sure I really know what to terms to use to search.

Background:

I have a DB that I am developing that tracks requirements for individuals. Each individual is assigned a auto serial key in a parent table. Each individual has satisfy many training requirements and has to file personnel information; there are many training and personnel categories. Each major category has an individual table and an auto serial key assigned to it and I think I have them attached to the primary key in the parent table. So the individuals table is the parent and the remaining tables are the children.

The Issue:

When I create a new record in the individuals table I cannot get another table (StripMap) to create a new record and display a google map of the individuals residential address. The StripMap table has an auto serial key and a container field. Inside the container field I have setup the google map which is pulling the address information from another table that contains personnel information.

I can't figure it out, maybe I am going about it the wrong way.

Thank you for your assistance.

[bcooney]

Each major category has an individual table

You should have all your Categories in one table. You need a table between Individuals and Categories.

When I create a new record in the individuals table I cannot get another table (StripMap) to create a new record and display a google map of the individuals residential address.

Why not just place a webviewer on the Individual form? Why do you need another table?

[Ron Cates]

By your description it sounds like you are linking an auto enter serial from the parent to an auto enter serial in the child table. What you should have is a foriegn key field in the child table that is not an auto enter. This field holds the serisl ID of it's parent record. That's how a relationship is established. All children of a record will have the parent's serial ID stored in thier foriegn key fields. So if the parent has a serial ID of 10 for instance, all related child records will have a 10 in the foriegn key field. The relationship from parent to child is made by linking the primary key field of the parent table to the foriegn key field of the child table.

[rexkwilliams]

Gentlemen,

Thank you for your replies. I will first try the foreign keys because if I cram all of the other fields into one table - well, I will have a hundred or so fields. I will let y'all know how it works out.

Thank you.

[bcooney]

Why would you have so many fields? Please read up on join tables.