-
" Created By: ORM Solutions
Version 1.0.3047.3 "
OK - This seems to be a version recently created by Matt Curland.
You will have to wait for Matt to respond.
-
Which version of NORMA are you using?
Ken
-
Each version of NORMA is specific to the Visual Studio version so NORMA for VS2015 will not run under VS2017.
-
The workaround for this problem is to import the Access database into SQL Server and then import the schema from SQL Server.
Ken
-
ORM is a formal language that happens to use diagrams to express some of its features.
The full name is "Formal Object-Role Modeling Language."
We use NORMA to express the details.
Using ORM diagrams without understanding their meaning is a waste of time.
If you want to understand why some misguided people might ...
-
You can ask questions here.
In 2016, I recruited a small team of volunteers to fix bugs in NORMA. The project resolved about 80 issues which included upgrading NORMA to VS2017 and then to VS2019.
About three years ago, the team became inactive - mainly because I contracted a serious illness that put me out of action for a long ...
-
Refer to the fact type diagram at the bottom of this post.
This is what it means:PersonNr is an entity type.
Reference Scheme: PersonNr has PersonNr_nr.
Reference Mode: .nr.
Data Type: Numeric: Signed Integer.
Fact ...
-
Thanks for the clarification.
You should be aware of several things:
1: ORM diagrams are really "First Order Logic In Pictures".
2: ORM diagrams hide a lot of detail because they are intended for use by modelers rather than as an explanation.
Please refer to the next post that has a seemingly simple binary fact type.
I ...
-
Hmm, an interesting approach.
The purpose of .orm files is to help people to store and to re-use editable information models.
So I'm curious to understand the problem that can be solved with un-editable .jpeg files?
It seems to me that generating .jpeg files from orm files removes 99% of their usefulness and value (if not ...
-
Have you tried to use NORMA to solve your problem?
Ken