Bug #45008 All foreign keys is not imported using ADO .NET Data Entities
Submitted: 21 May 2009 13:28 Modified: 19 Sep 2009 8:52
Reporter: Morten Andersen Email Updates:
Status: No Feedback Impact on me:
Category:Connector / NET Severity:S2 (Serious)
Version:6.0.3 OS:Windows (Vista 32)
Assigned to: Assigned Account CPU Architecture:Any

[21 May 2009 13:28] Morten Andersen
I have 3 tables. User, Contact, and System

User.ContactID FK Contact.ContactID
Contact.SystemID FK System.SystemID

The relationship between User and Contact gets "imported" using the ADO designer in Visual Studio 2008, but there is no relationship between Contact and System.

How to repeat:
1. Create 3 tables, whree table1 has a fk to table2, and table2 has a fk to table3
2. Create a .edmx and select all 3 tables and import them
3. You will now see that table1 and table2 is connected, but not table3
[23 May 2009 13:49] Morten Andersen
There is some strange behavior here. I am not able to pin out exactly what causes the problem. Just try to create tables with foreign keysm, then try to design it from visual studio, and you should get unexpected behavior pretty fast.
[19 Aug 2009 8:52] Tonci Grgin
Hi Morten and thanks for your report.

Please attach full solution and DDL/DML script I can import so I can check on this.
[19 Sep 2009 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".