The ORM Foundation

When you have a role selected, there should be a ValueRange entry listed in the Properties window, through which you can enter the value constraint.

Sorry for the delayed reply. As you noted, our current generation process is not accounting for these situations correctly. We have identified what the problem is and how to address it, and we are in the process of doing so as part of some larger overall changes to our generation process. Once the fixes for these issues are in place, I will post ...

The DDL should include a parameter with that name. The fact that it doesn't is a bug that will be fixed in our next release (the fix should be available in the Subversion repository within the next few days). As for why the schema creation doesn't occur within a transaction, that is a SQL Server issue. If I remember correctly, they don't ...

Just to further clarify this, the additional options in the context menu come from having either ''East Asian'' or ''Complex Script'' languages support enabled in Windows. Pre-Vista (e.g. Windows Server 2003 and Windows XP) have these turned off by default (at least in the English versions), but Vista always has these features enabled permanently ...

If you put on an external uniqueness constraint and connect it to the correct roles, you should be able to set ''IsPreferredIdentifier'' to true in the Properties window. With the ORM2 notation, we are using a double line in the circle to represent the preferred identifier uniqueness constraint, and a single line to represent a ''normal'' ...

Yes, it it possible to add additional pages to your model. At the bottom of the diagram, there should be a gray bar. At the left side of this bar will be a tab for the current page, which will have the ''ORM'' in red and the name of the page. If you right click in this area (either on the tab or the bar), you should be able to choose ''New Page'' ...

Those paths are just the locations of the source files for ORMCustomTool on the machine where that release was built. It looks like for some reason it is failing to compile the OIALtoPLiX.xslt file. If you send me your copy of that file, I can take a look at it and see if I can figure out why that is happening. Alternatively, we should be posting ...

Are the other values correct? Specifically, SourceInputFormat should be ''OIAL'' and ProvidesOutputFormat should be ''PLiX''. You may want to try doing a repair on the NORMA installation (from the ''Add or Remove Programs'' dialog).

OK, I received the file and I think I see what the problem is. The C# code is generated from the PLiX representation of the generated object model, but I don't see a PLiX file listed in your .csproj file. When you selected C# as one of the outputs you wanted, the ORMCustomTool should have automatically enabled the PLiX output as well, but for ...

Interesting... Could you send me the .csproj file for that project?