Split DB Relationships

[PatientZer0]

I have been working with Access for a few years now and have recently come
across an issue, about which I have not been able to find any discussion.

I am currently working with a split database in which I have placed a few
static lookup tables in the frontend for performance reasons; however, I am
unsure as to how the relationships for these tables should be made.

Should the “real†tables in the front end be duplicated in the back end
(aliased?) with the relationships drawn there? Would they need to be renamed
or referenced in a specific way to access the FE versions? OR should the
“real†tables only exist in the FE with specific relationships made in the FE?

 

[Douglas J. Steele]

It's not possible to create relationships between tables that exist in two
different database files.

If the reason for relationships is to enforce referential integrity, I'm
afraid you're out of luck. While you can have copies of the tables in the
back-end, any relationships you may set up with those tables won't be used
if you're using the front-end copies.

 

[John W. Vinson]

I am currently working with a split database in which I have placed a few
static lookup tables in the frontend for performance reasons; however, I am
unsure as to how the relationships for these tables should be made.

Should the “real” tables in the front end be duplicated in the back end
(aliased?) with the relationships drawn there? Would they need to be renamed
or referenced in a specific way to access the FE versions? OR should the
“real” tables only exist in the FE with specific relationships made in the FE?

Relationships can only exist between tables in the same database. Frontend
lookup tables cannot be related to backend tables.

One possible solution would be to have the "master" lookup tables stored in
the backend, and have some mechanism to upload them to the frontend when they
are changed.