Enforcing ref. integrity between MDB files

[Dirk]

Greetings from Canada.

This may sound like a stupid question. Is it possible to
enforce referential integrity between tables stored in
two separate Access MDB files?

For example, I have tables in database #1 that contain
spatial information. One of these tables is called SITE.
In database #2 I have a SAMPLE table that I wish to join
to the SITE table in database #1 and enforce referential
integrity (cascade update only). Database #1 is
a "geodatabase" used by GIS software, but is actually a
MDB file that can be opened and edited in Access.

I am only able to join the tables (the SITE_ID field is
common to both tables), but the referential integrity
options are dimmed out. Is there a way around this?

Thanks in advance.


Sincerely,
Dirk

Winnipeg, Canada

 

[Adrian Jansen]

The simple answer is no, you cannot.

--
Regards,

Adrian Jansen
J & K MicroSystems
Microcomputer solutions for industrial control

 

[Douglas J. Steele]

It's not possible.

 

[John Vinson]

Is it possible to
enforce referential integrity between tables stored in
two separate Access MDB files?

As noted, the answer is a flat No.

The reason is pretty clear if you think about it: if you have a
relational constraint defined in ABC.MDB on a pair of tables from
ABC.MDB and XYZ.MDB, there is nothing to prevent someone from opening
XYZ.MDB directly (or from QRS.MDB) and making a change to the data
which violates that constraint. Since ABC.MDB isn't even open it is
powerless to enforce the constraint.