I'm trying to get NORMA working again after an odd Visual Studio 2005 error in version 8.0xxx, on winXP 2002, sp2 (I did the repair on the .NET framework 2.0 as suggested, and that is working again), also with the latest NORMA_VS-2007-11CTP.VS2005. removed plix, reinstalled it, removed 'Microsoft DSL Tools Redistributable' and reinstalled it. The ...
''Where did that come from'' is what I said to myself on seeing NORMA listed in the online help for VS 2008 (though the version I have running on this notebook).
I loaded up VS 2008 late last year. I loaded the Dec drop (Nov 07 release), of NORMA for VS 2008 about that time. Hadn't had much time to use it, though.
Today, I was ...
Here is an image to illustrate the previous post:
When a role is set as Mandatory the constraint name in the Relational View becomes ''Constraint'' instead of ''InternalUniquenessConstraintXX''.
Company(code) ___*-|-___ Subscription(Nr)
Company has DriverTech Subscription.
Each Company has exactly one DriverTech Subscription.
For each DriverTech Subscription, at most one Company has that DriverTech Subscription.
but Database table:
Company (Company_Code, Company, ...)
UNLESS I provide a name for the Role marked as ...
Could you please post what the verbalization is currently coming out as, and what part of it is wrong (if it is not obvious)? Thanks.
I could explain what this is, but if Ive done it well it wont need extra explanation :)
Verbalization of column names does not work properly for a 1 to 1 fact between entities when a role is Mandatory.
To get around this, I found that I must set the ''Name'' value on the mandatory Role of the fact.
Haha. I don't think NORMA/Neumont folks are on any easy track for the new book. -Matt