Visio Database Model - child has parent optional check box is grayed out. I'm using idef1x notation and it shows a circle on one end of the relationship and diamond on the other end. I need child has parent Checkbox Optional to be unchecked. I'm not able to do that because it's grayed out. 

It stays checked unless I set Relationship type = Identifying. 

I want

Relationship Type = Non-identifying - Migrate the key using FK not PK

Child has parent (Optional) = unchecked

Cardinality = one or more 

How can I get Child has parent to enable to I can uncheck it?

If I pretype the FK from the Parent into the Child it gives me what I want. I was hoping I could do it with out pretyping the keys

The only way I can see to accomplish this is to disconnect the association on the Relationship. Not sure why we make that unavailable or if that's intentional. It could be because we treat it as a mandatory non-identifying relationship but I'm not sure.

• Marked as answer by Jennifer ZhanModerator Friday, October 08, 2010 8:15 AM

The only way I can see to accomplish this is to disconnect the association on the Relationship. Not sure why we make that unavailable or if that's intentional. It could be because we treat it as a mandatory non-identifying relationship but I'm not sure.

• Marked as answer by Jennifer ZhanModerator Friday, October 08, 2010 8:15 AM

The only way I can see to accomplish this is to disconnect the association on the Relationship. Not sure why we make that unavailable or if that's intentional. It could be because we treat it as a mandatory non-identifying relationship but I'm not sure.

• Marked as answer by Jennifer ZhanModerator Friday, October 08, 2010 8:15 AM

The only way I can see to accomplish this is to disconnect the association on the Relationship. Not sure why we make that unavailable or if that's intentional. It could be because we treat it as a mandatory non-identifying relationship but I'm not sure.

• Marked as answer by Jennifer ZhanModerator Friday, October 08, 2010 8:15 AM

The only way I can see to accomplish this is to disconnect the association on the Relationship. Not sure why we make that unavailable or if that's intentional. It could be because we treat it as a mandatory non-identifying relationship but I'm not sure.

• Marked as answer by Jennifer ZhanModerator Friday, October 08, 2010 8:15 AM

The only way I can see to accomplish this is to disconnect the association on the Relationship. Not sure why we make that unavailable or if that's intentional. It could be because we treat it as a mandatory non-identifying relationship but I'm not sure.

• Marked as answer by Jennifer ZhanModerator Friday, October 08, 2010 8:15 AM

The only way I can see to accomplish this is to disconnect the association on the Relationship. Not sure why we make that unavailable or if that's intentional. It could be because we treat it as a mandatory non-identifying relationship but I'm not sure.

• Marked as answer by Jennifer ZhanModerator Friday, October 08, 2010 8:15 AM

Is there an update on this? It indeed seems that typing the foreign key field name first and then establishing the relationship makes this possible. Checking/unchecking Req'd on the foreign key then automatically checks/unchecks Optional on the relationship.

Is this perhaps a bug in Visio that checking Req'd on the FK does not affect the Optional checkbox if the field was automatically created by establishing the relationship.

(In general terms, clearly if the FK field is a required field, the parent is not optional.)

This seems to be a timing issue, at least in Visio 2010 (Premium). Once you have the relationship defined normally (and have the original problem mentioned), this seems to work:

> In the Definition tab, "Disconnect" the associated fields

> In the Miscellaneous tab, uncheck the "Child has parent/Optional" box (it's now active); then choose "Non-identifying"

> Click somewhere off the Relationship object

> Select the Relationship obeject again, go to the "Definition" and now you can "Associate" the related fields again as they should be

Let's hope the Visio team is reading these so they can fix such a silly bug!

 

= M =

 

Thanks, very helpful. It is extremely annoying. I hope it gets fixed.

Brillant.