relational integrity is grayed out on 1-to-1 relationship

[mary r]

I'm trying to create referential integrity with at least cascading updates.
Table 1 is linked; table 2 is local. Relationship is between primary key in
table 1 and a uniquely-indexed field in table 2.

When I create the relationship, it comes up automatically as 1-to-1, but the
relational integrity boxes are disabled. Can anyone shed some light on this?
I really need to have an updateable query using these tables.

Thanks in advance!

 

[BruceM]

You can't enforce referential integrity on a relationship that includes a
linked table.

This may shed some light on read-only queries:
http://allenbrowne.com/ser-61.html

If the query was updateable you would be able to delete or change the join
field in table 2. There may be other reasons, but this is the one that
occurs to me why it is not updateable.

One option is for the user interface to be a form based on table 1 with a
subform based on table 2.

 

[Dirk Goldgar]

I'm trying to create referential integrity with at least cascading
updates.
Table 1 is linked; table 2 is local. Relationship is between primary key
in
table 1 and a uniquely-indexed field in table 2.

When I create the relationship, it comes up automatically as 1-to-1, but
the
relational integrity boxes are disabled. Can anyone shed some light on
this?
I really need to have an updateable query using these tables.

You can't enforce referential integrity across databases. Only local tables
can have referential integrity enforced.

Perhaps some other approach will accomplish what you need.

 

[mary r]

Thanks, guys. I'm grafting functionality onto an existing system, so I can't
really move the tables in question. Since I only need one field from one of
the tables, I've dropped it from the query and am using DLookup for that one
flag. To update it on the form, the user double-clicks and I use SQL to
change it in the source table, and this is working just fine. DLookup hasn't
been unduly slow so far, maybe because it's only grabbing one field.

Thanks again!