Cascading update help.

[Paul]

I need two fields in diffent tables to match when data is inputed into one of
them. I figued the way to do this is enforce ref and update
cascades.....except its not working!!!

Both tables have the same field type for a primary key its a unique 5 digit
ref number. The records I want to update should be in both tables. The fields
I want to update is a date field and a combo box field.

I need it so a user enters their date in the form and without them having to
do anything, enter the same data in the other table. Is this simple?

Also I'll need users to make new records as well that will create in the 2
tables,. I know this is sounds redundent, buts the only way around it.

Any help you can give will be awesome!! Anymore info needed just ask.
Thanks!!!!!!

 

[Rick Brandt]

I need two fields in diffent tables to match when data is inputed
into one of them. I figued the way to do this is enforce ref and
update cascades.....except its not working!!!

Both tables have the same field type for a primary key its a unique 5
digit ref number. The records I want to update should be in both
tables. The fields I want to update is a date field and a combo box
field.

I need it so a user enters their date in the form and without them
having to do anything, enter the same data in the other table. Is
this simple?

Also I'll need users to make new records as well that will create in
the 2 tables,. I know this is sounds redundent, buts the only way
around it.

Any help you can give will be awesome!! Anymore info needed just ask.
Thanks!!!!!!

Table relationships do not automatically cause data to appear in other tables.
They only enforce rules about what is entered in those tables.

You might be getting confused with two other behaviors in Access.

1) When such related tables are used in a form/subform setup the MasterLink and
ChildLink properties will automatically propagate the linking field values from
the main from into any new records created in the subform. The user still has
to initiate the creation of the subform record though.

2) If Cascade Update/Deletes are enabled in the relationship a change to the key
field in the parent table will cause that change to be propagated to the
matching records in the child table and if a parent record is deleted the
associated child records will automatically be deleted.

 

[Paul]

Oh.

So is there a way to do this automaticly? It doesn't look like there is.

Thanks anyway

 

[tina]

usually, in a properly normalized database, you do not enter the same data
in two different tables. there are exceptions to that rule, of course, but
it's very possible that your database is simply structured incorrectly.
suggest you post a description of your tables/relationships, along with a
simple explanation of what you're using the database to do, in the newsgroup
microsoft.public.access.tablesdbdesign
and ask for comments on your design. you may find that by adjusting your
structure, you don't need to enter the same data in two tables after all.

hth