I would first check my relationships. A one-to-one is where, say, you have
one salesman, one product to sell. In that case, you usually don't need but
one table unless it is huge and then you might split into two. One-to-many
is, say, one salesman, many products. In that case you want the primary key
in the one table to be the foreign (not primary) key in the ohter tables. If
you have many-to-many, say many salesmen, many products, you need tables in
between those tables to connect them together or you won't get good results.
Cascade updates and deletes will only update or delete what is in the
relationship.
--
Milton Purdy
ACCESS
State of Arkansas


"Kelli" wrote:

I am relatively new to Access, and am currently creating a new Database, four
tables, definately obeying the first two normal forms. The main table (named
tblCO) has a field named Conc# that is designated as the primary key. I need
to join the remaining three tables to tblCO so that when a value is input
into the Conc# field, it cascades to the other three table.
I will ultimately build a form for users to work with in data input/editing,
but am using the tables myself during the developement stage. As I put in
data, I can not get the Conc# field values to propogate to the other tables.
I have joined them and have selected Referential Integrity and Cascade Update
and Cascade Delete.
What might I be doing incorrectly.
Thank you for you interest in my problem
Kelli