VEA Error C2006: '(null)' Predicate has no uniqueness constraint.

[Maria]

I am having problems resolving errors reported by the Model Error Check. I get nine *identical* error messages

<myfile.vsd> : error C2006: '(null)' Predicate has no uniqueness constraint

I am looking for a quick way to identify all the offending predicates one by one. Yes I know that I can right-click the error message in the output window and clidk "Go To Source". But if the object is not on the drawing I get this message: "This predicate has not been placed on the diagram. To view information about this predicate, please drag it to the diagram". This does not help because I still get no clue what "this predicate" refers to

All I came up with so far is to make a fact report and then hunt for all records that do NOT have any constraint. Unfortunately, for a fact record that does not have any constraints the 'constraints' line is simply missing from the report. This means that the record layout is not consistent and I cannot do a straightforward search for lines with zero constraints; instead I have to check every record in the report to see if the constrains line is missing - not exactly efficient.
I sincerely hope there is a better way - any suggestions welcome

 

[Aravind Hande]

I am having problems resolving errors reported by the Model Error Check. I

get nine *identical* error messages:

<myfile.vsd> : error C2006: '(null)' Predicate has no uniqueness constraint.

I am looking for a quick way to identify all the offending predicates one

by one. Yes I know that I can right-click the error message in the output
window and clidk "Go To Source". But if the object is not on the drawing I
get this message: "This predicate has not been placed on the diagram. To
view information about this predicate, please drag it to the diagram". This
does not help because I still get no clue what "this predicate" refers to.

All I came up with so far is to make a fact report and then hunt for all

records that do NOT have any constraint. Unfortunately, for a fact record
that does not have any constraints the 'constraints' line is simply missing
from the report. This means that the record layout is not consistent and I
cannot do a straightforward search for lines with zero constraints; instead
I have to check every record in the report to see if the constrains line is
missing - not exactly efficient.

I sincerely hope there is a better way - any suggestions welcome.

The following steps should help:

Create a temporary page (right click on the page tab and select insert page
menu option) and re-order the pages so that this new page is the first page
in the model.

Then drag all the facts onto this page and then run the model error check
again. Right clicking the error message should display the offending
predicate on this new page.

Once you have fixed all the errors (by adding uniqueness constraints), you
can then get rid of the temporary page (just make sure you don't delete the
facts).

Note: The same fact can be displayed on multiple pages, without any
problems.

Hope this helps.

Aravind Hande

 

[Maria]

Yes - that is a much better way of finding the errors. It had slipped my mind that it is possible to select/drag all the facts onto a page in one go. Thanks
Maria