There is already an implicit frequency constraint of "exactly one" on any unary predicate, i.e., there's already an implicit functional uniqueness constraint on the role, and the tool is apparently set up to prevent making that constraint explicit. But you can use the "add constraints" dialog to add the uniqueness constraint explicitly.
Andy
-----Original Message-----
From: geverest@... [mailto:geverest@...]
Sent: Monday, August 02, 2004 1:27 AM
To: jcm@yahoogroups.com
Subject: [JCM] Frequency constraint on a Unary predicate
From: geverest@... [mailto:geverest@...]
Sent: Monday, August 02, 2004 1:27 AM
To: jcm@yahoogroups.com
Subject: [JCM] Frequency constraint on a Unary predicate
I am using VisioEA 2003 and am attempting to define a frequency constraint
on a unary predicate.
I want to specify exactly one. When I leave the minimum at 1, and change
the maximum from 2 to 1,
the system dims out the 'OK' button and I am unable to define that
particular frequency constraint.
This would appear to be a bug in the system. Anyone encountered this?
-gord.everest
~~~~~~ Sponsor's Message ~~~~~~~~~~~~~~~~~~~~~
Would you like to learn more about Object-Role Modeling (ORM)?
Then check out InConcept's ORM Seminars!
These seminars will focus on the use of Object-Role Modeling to correctly model your business data requirements. Each day also contains "hands on" labs where students practice the technique while ORM-certified instructors give one-on-one assistance.
Custom on-site courses are also available.
For more information, please see http://www.inconcept.com/training/ormseminar.html or e-mail training@....