I am having a look at this with the guys.
In the past I've worked around this issue by adding a surrogate integer PK to the parent table that results in a single relationship to the child table but this introduces other issues that Id like to avoid.
Attached is a simple ER diagram illustrating the relationship I'm trying to implement (relationship 5) in the diagram and a screen shot of the DDT error when trying to deploy.
I’m having a problem deploying a database with a compound foreign key relationship. DDT will allow you define two relationships to set up the foreign key relationship between tables TableAxTableB and TableC in the attached example but fails when you try to deploy it.
-Larry