Split database and relationships

[Gavx]

When the database is split between front end and back end where do you create the relationships? In the front or back end?

 

[theDBguy]

Hi. Relationships have to be created where the tables are defined. Normally, that means the back end.

 

[Gavx]

thanks

 

[zeroaccess]

You will also notice that if you design a single-file database and then later split it, the relationships will move to the back-end with the tables.

 

[Pat Hartman]

To expand on the answer and help you to understand why,

The relationships are always defined in the database where the physical tables exist. This allows the relationships to be enforced regardless of what FE makes changes to the tables.

For multi-user Access apps, each user has his own personal copy of the FE but all the data changes happen in the BE and so if you made a mistake and one of the FE's didn't have the relationships correctly defined, that app could break the others if did something to violate the RI you defined.

This concept is universal. If your tables are in SQL Server, that database is where the relationships are defined.

 

[The_Doc_Man]

True for ORACLE too.

 

[Pat Hartman]

I didn't mean to imply that the rule was limited to Access and SQL Server. It applies to ALL RDBMS'

 

[Gavx]

Thanks