PMFJI, I have a few comments/suggestions.
You should read Microsoft Access Tables: Primary Key Tips and Techniques (<<-- ** Important)
When I name fields in a table, they would look like
tblClientGender
----------------
cgClientGenderID_PK - Autonumber (PK)
cgcClientID_FK - Number (Long Integer) (FK to tblClient)
cggGenderID_FK - Number (Long Integer) (FK to tblGender)
cgOther - Short Text
The table name has "tbl" as a prefix.
The PK field has a suffix of "_PK"; a foeign key field has a suffix of "_FK". (Ajax uses "PK'/ "FK" suffixes)
The suffix "ID" (for me) means it is a numeric type field (autonumber/Long).
I like that you (the OP) used a prefix (example "cg") to indicate what table the field is in.
For a table I named "tblEmployee_Name_Def", I use field prefixes of "end_"..... (as in "end_FName")
You might find it helpful to first design the tables/relationships using a whiteboard, a window or even paper & pencil BEFORE jumping into Access. It is easier to make changes and to see the "big picture" or at least it is for me (I use a big window).
----------------------------------------------------------------------------------------------------
About your table design....
Most of the field names in tblGender are data.
The reason this design is bad is that to add another gender "type", say "Hermaphrodite" (sorry, couldn't come up with another example), first you have to edit/change the table.
Then you have to edit the queries, forms, reports & then the code. All this just to add one more option.
If you have a table
Code:
tblGender
----------
gGenderID_PK - Autonumber (PK)
gGender - Short Text
all you have to do is add the name to the table. Everything else doesn't have to change.
I'll step aside now... Good luck with your project.......