﻿<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>StrataFrame Forum » StrataFrame Database Deployment Toolkit » Issues  » Compound Foreign Key</title><generator>InstantForum 2017-1 Final</generator><description>StrataFrame Forum</description><link>http://forum.strataframe.net/</link><webMaster>StrataFrame Forum</webMaster><lastBuildDate>Sun, 31 May 2026 02:32:31 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Compound Foreign Key</title><link>http://forum.strataframe.net/FindPost28218.aspx</link><description>I checked with Trent, et al and this apparently got overlooked. It is now on the todo/to-test list.  I'll let you know when I get more information.</description><pubDate>Tue, 31 Aug 2010 18:03:20 GMT</pubDate><dc:creator>Greg McGuffey</dc:creator></item><item><title>Compound Foreign Key</title><link>http://forum.strataframe.net/FindPost3538.aspx</link><description>&lt;DIV class=Section1&gt;&lt;P class=MsoNormal&gt;&lt;SPAN style="FONT-SIZE: 8pt; COLOR: #1f5080"&gt;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. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=MsoNormal&gt;&lt;SPAN style="FONT-SIZE: 8pt; COLOR: #1f5080"&gt;-Larry&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=MsoNormal&gt;&lt;?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/P&gt;&lt;P class=MsoNormal&gt;&lt;?xml:namespace prefix = v ns = "urn:schemas-microsoft-com:vml" /&gt;&lt;v:shapetype id=_x0000_t75 stroked="f" filled="f" path=" m@4@5 l@4@11@9@11@9@5 xe" o:preferrelative="t" o:spt="75" coordsize="21600,21600"&gt;&lt;v:stroke joinstyle="miter"&gt;&lt;/v:stroke&gt;&lt;v:formulas&gt;&lt;v:f eqn="if lineDrawn pixelLineWidth 0 "&gt;&lt;/v:f&gt;&lt;v:f eqn="sum @0 1 0 "&gt;&lt;/v:f&gt;&lt;v:f eqn="sum 0 0 @1 "&gt;&lt;/v:f&gt;&lt;v:f eqn="prod @2 1 2 "&gt;&lt;/v:f&gt;&lt;v:f eqn="prod @3 21600 pixelWidth "&gt;&lt;/v:f&gt;&lt;v:f eqn="prod @3 21600 pixelHeight "&gt;&lt;/v:f&gt;&lt;v:f eqn="sum @0 0 1 "&gt;&lt;/v:f&gt;&lt;v:f eqn="prod @6 1 2 "&gt;&lt;/v:f&gt;&lt;v:f eqn="prod @7 21600 pixelWidth "&gt;&lt;/v:f&gt;&lt;v:f eqn="sum @8 21600 0 "&gt;&lt;/v:f&gt;&lt;v:f eqn="prod @7 21600 pixelHeight "&gt;&lt;/v:f&gt;&lt;v:f eqn="sum @10 21600 0 "&gt;&lt;/v:f&gt;&lt;/v:formulas&gt;&lt;v:path o:connecttype="rect" gradientshapeok="t" o:extrusionok="f"&gt;&lt;/v:path&gt;&lt;o:lock aspectratio="t" v:ext="edit"&gt;&lt;/o:lock&gt;&lt;/v:shapetype&gt;&lt;v:shape id=_x0000_i1025 style="WIDTH: 291.75pt; HEIGHT: 159.75pt" coordsize="21600,21600" o:ole="" type="#_x0000_t75"&gt;&lt;v:imagedata o:title="" src="SFError_files/image001.emz"&gt;&lt;/v:imagedata&gt;&lt;/v:shape&gt;&lt;/P&gt;&lt;/DIV&gt;</description><pubDate>Tue, 31 Aug 2010 18:03:20 GMT</pubDate><dc:creator>Larry Caylor</dc:creator></item><item><title>RE: Compound Foreign Key</title><link>http://forum.strataframe.net/FindPost28212.aspx</link><description>ping...</description><pubDate>Tue, 31 Aug 2010 12:23:27 GMT</pubDate><dc:creator>Larry Caylor</dc:creator></item><item><title>RE: Compound Foreign Key</title><link>http://forum.strataframe.net/FindPost28069.aspx</link><description>Hi Larry.&lt;/P&gt;&lt;P&gt;I am having a look at this with the guys.</description><pubDate>Mon, 23 Aug 2010 17:08:03 GMT</pubDate><dc:creator>Ivan George Borges</dc:creator></item><item><title>RE: Compound Foreign Key</title><link>http://forum.strataframe.net/FindPost28066.aspx</link><description>This is still an issue in the current version. While the DDT will let you define multiple relationships to implement a compound foreign key, the DDT will not deploy it. Also if you try to import a database with a compound foreign key, the DDT will only&amp;nbsp;import the first relationship it sees.&amp;nbsp; &lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;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.</description><pubDate>Mon, 23 Aug 2010 15:24:09 GMT</pubDate><dc:creator>Larry Caylor</dc:creator></item></channel></rss>