Linked Object - bug with multi-column foreign keys
In the case of a foreign key based on > 1 columns, Add Linked Object seems to be not correctly interpreting the relation. For example:
ALTER TABLE [dbo].[EQUIP_LEASE] ADD CONSTRAINT [FK_EQL_SUB_STATUS_CODE] FOREIGN KEY([STATUS_CODE], [SUB_STATUS_CODE])
REFERENCES [dbo].[EQUIP_SUB_STATUS_CODE] ([STATUS_CODE], [SUB_STATUS_CODE])
So, if we have EQUIP_LEASE on the query designer, and then click the Linked Objects button, I'd expect to see:
--> EQUIP_SUB_STATUS_CODE(STATUS_CODE,SUB_STATUS_CODE), and clicking it would add that table with a join on both columns.
However, what you actually see is two separate items:
--> EQUIP_SUB_STATUS_CODE(STATUS_CODE)
--> EQUIP_SUB_STATUS_CODE(SUB_STATUS_CODE)
....and when clicked, it adds the table, but only with a join on that single column.
ALTER TABLE [dbo].[EQUIP_LEASE] ADD CONSTRAINT [FK_EQL_SUB_STATUS_CODE] FOREIGN KEY([STATUS_CODE], [SUB_STATUS_CODE])
REFERENCES [dbo].[EQUIP_SUB_STATUS_CODE] ([STATUS_CODE], [SUB_STATUS_CODE])
So, if we have EQUIP_LEASE on the query designer, and then click the Linked Objects button, I'd expect to see:
--> EQUIP_SUB_STATUS_CODE(STATUS_CODE,SUB_STATUS_CODE), and clicking it would add that table with a join on both columns.
However, what you actually see is two separate items:
--> EQUIP_SUB_STATUS_CODE(STATUS_CODE)
--> EQUIP_SUB_STATUS_CODE(SUB_STATUS_CODE)
....and when clicked, it adds the table, but only with a join on that single column.
Thank you for your report.
We will correct this behavior in the next version.