Why do you need separate files? (it complicates the relationship design)
You describe a table, Fabrics_Library, but then go on to describe a relationship between Program_Fabrics and Fabrics. Is Fabrics and Fabrics_Library the same table?
What fields are used in what kinds of relationships in each of these relationships?
What is the purpose of each of these tables?
What kind of data do you need to "cascade" from one table into the others? (Often proper relationship/table structure precludes the need for cascading updates) and why?
Thought as much.
Unfortunately I inherited this octopus.
The users require this info at the style level and there is also a data export at the style level.
The data has been added to the Translations::Fabric_Library table and is relevant to fabric we source.
I've included screen shots of the relationships and linking for the DB's and tables.
The heirarchy is..
TranslationsDB ---> ProgramsDB ---> StyleBookDB