Please read my responses to your earilier posts, where I talk about how to
help us help you (Introduction, Programming Automation)

Note the following:

Tables -- store data (they are not for data entry)
Relationships -- tie tables together using primary and foreign keys
Forms -- Display data, add data, edit data, and sometimes (with caution)
delete data
Queries -- Table like in that they select data to display in forms or
reports.
Reports -- Print out data or in preview mode can display data
Macros -- code like things that allow those of us that are not programmers
to do some really neat (dangerous) things.
Modules -- this is where the VBA code lives.

Did I mention tables are not for data entry?

sub-forms are a powerful friend.
-------------------------------------------------------------------------------------------------------snip
I save the data, and close it

------------------------------------------------------------------------------------------------------snip

the 'bell ringer' is:  "close it".

To get the 'Cascade' of key fields you are wanting you have to use forms and
sub-forms.

For those on the list that don't speak 'military'

LstBldTyp                        ????
LstClnc                            ????
LstGndr                            gender
LstKeyBilletO                    key billet authorized
LstRankList                        list of pay grades Enlisted-1 to
Enlisted-9 and Officer-1 to Officer-10 (or their equivelent)
LstSwimClass                    Swiming qualification level
LstWorkSection                Work Section
LstWpnsQual                    Level of Weapons Qualification

TblG3Account                    not a clue
TblG3Basic                        SSN(Key), FirstName, LastName, other stuff
TblG3Clnc                            not a clue
TblG3Med                           something to do with medical ?????
TblG3NoK                        1:Many --> Next of Kin (each member can have
several Next of Kin listed on their emergency data form (e.g. Wife, mother,
father, brother)
TblG3NonResPME                    Non Reserve PME (??? I have not a
clue)(NAC)
TblG3OIF0406TrngALL    not a clue
TblG3OIF0406TrngSel       not a clue
TblG3Promo                       1:Many --> Promotions each member is
promoted (demoted, some marines 'play rough on nights out' ;>,) several
times :: sample fields PromotionID, SSN, date, NewPaygrade, Notes.
TblG3Recall                        1:Many --> (Maybe)  Each Marine could be
recalled on several occasions and each recall could have unique data
elements attached.
TblG3ResPME                     not a clue
TblG3Skills                          1:Many --> (even if Marines ;>, each
may have more than one skill)
TblG3Training
TblG3Uniform                    1:Many --> each member may be (issued)
several different uniforms. May be paid for uniforms more than once.  May be
assigned a different Uniform allowance at different times.
TblG3Vehicle
TblG3Weapons                1:Many --> each member may be qualified in many
weapons:: sample fields WeaponQualID, SSN, date, (LstWpnsQualID, from
LstWpnsQual)

So, In general your tables are 'almost correct' (assuming you have a 1:many
relationship in the tables I cannot decipher)
You want to use forms and sub-forms to enter data (Link parent-child fields)
You probably want to use a tabbed control to contain the various sub-forms.

That is about all the damage this old submariner can do with the information
provided.

Ed Warren.