S
Steve_Da_B
I have two tables in SQL Server. Table FIRST has a primary key called ID. Table SECOND has a primary key called ID. There's a relationship between the two, so FIRST.ID is PK to FK SECOND.ID
Ie, for every record in SECOND, there MUST be a record in FIRST, for every record in FIRST there may be zero or one records in SECOND (since ID in Second is unique, it can be zero or one)
However, when reverse engineering in Visio (2002, SP2), it shows the relationship as one-to-one: the optionallity on the SECOND table end of the relationship is wrong
I've even tested it in the database (inserting a record into FIRST does not require a record in SECOND) just to make sure I am not missing anything.
Ie, for every record in SECOND, there MUST be a record in FIRST, for every record in FIRST there may be zero or one records in SECOND (since ID in Second is unique, it can be zero or one)
However, when reverse engineering in Visio (2002, SP2), it shows the relationship as one-to-one: the optionallity on the SECOND table end of the relationship is wrong
I've even tested it in the database (inserting a record into FIRST does not require a record in SECOND) just to make sure I am not missing anything.