Thank you, and I have lowered my expectations as you suggest, but not my
enthusiasm

"John W. Vinson" wrote:

On Tue, 27 Apr 2010 11:00:01 -0700, 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.

That's not how relationships work! A relationship *prevents* adding invalid
records; it doesn't automagically create a new record.

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.

Use a form with subforms from the start. If you have a child table displayed
in the subform using Conc# as the Master/Child Link Field it will fill in
automatically for you. Table datasheets are for data storage; they are *very
limited* when it comes to data entry.

As I put in
data, I can not get the Conc# field values to propogate to the other tables.

It won't, and you shouldn't expect it to do so. After all some parent records
might not HAVE any child records; some might have one; some might have
thousands. Create the child record when you have data to put in the child
record (using a Subform); there is no need to create an empty "placeholder"
record.


I have joined them and have selected Referential Integrity and Cascade Update
and Cascade Delete.

Cascade Update will update an existing linked child record when you change the
value of the primary key field in an existing record in the table (something
that should rarely or never be done, since primary keys should be stable).

What might I be doing incorrectly.

Just your expectation.
--

John W. Vinson [MVP]
.