You can certainly create the joins, but you have to manage the integrity of
the data yourself: making sure you cannot delete/edit data in the primary
table that's referenced by the secondary, or insert/edit data in the
secondary that doesn't match the primary.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.


".Len B" wrote in message
...
So I won't be able to create this relationship then because
each table will be in a different, the existing one and the
one from the split.

I suppose that means that I'll need to handle RI by joins
in queries.

--
Len
__________________________________________________ ____
remove nothing for valid email address.
"Allen Browne" wrote in message
...
| That's correct. Access is unable to enforce RI across different data
files.
|
| When you split your database, the relationships exist in back end.
|
| --
| Allen Browne - Microsoft MVP. Perth, Western Australia
| Tips for Access users - http://allenbrowne.com/tips.html
| Reply to group, rather than allenbrowne at mvps dot org.
|
|
| ".Len B" wrote in message
| ...
| I have a db that will eventually be split.
| tblChild has PK ChildID and is a linked table
| tblNote has FK ChildID (long).
| Relationship window will allow me to drop PK on FK and declares
| a one-to-many relationship. The Referential Integrity check
| boxes are unavailable. If I create the relationship anyway
| both ends of the line have just a small blob rather than
| a 1, many or arrow.
|
| I am guessing there's nothing I can do about it and that it is
| happening because the table on the one side is external. Right?
|
| What happens when I split and the tables are in different
| back ends? Am I in trouble?
|
| --
| Len
| __________________________________________________ ____
| remove nothing for valid email address.
|