Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Splitting databases and relationships

Status
Not open for further replies.

mlabac

Programmer
Jan 22, 2004
23
US
I have my database split, tables in one (Data DB), forms query’s and modules in the other (Application DB) . In the application DB, including my linked tables to the Access Data DB, I also have linked tables to SQL Server and dB tables. This leads me to two questions. Where should I define my relationships? It would seem to make since to create the relationships in the Data DB. But by doing this I would have to create my links to the SQL tables and dB tables in the data DB if I want to create relations from those tables to the access tables. Which is my next question. Should I create my links to the sql and dB tables in the Data DB and then link them twice?

Right now I have my relationships created tin the Application DB.

Thoughts?

 
Don't link twice. Because of the mix of data sources you will have to create your relationships that involve multiple data source in your application front end. The relationships that only involve the tables in the access back end can be defined in that back end. Just like relationships that only involve the SQL server tables can be defined in the SQL server back end database.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top