Similar Questions

• How can I Data Modeler does not generate constraints on NNC_ tables?

  Hi all

  Unfortunately I have not found the answer using Google ;-)

  When I generate my DDL scripts on my model on some tables Data Modeler (version 4.0.0) automatically generates constraints on the columns of the table "NNC_" for example:

  CREATE TABLE STG_DURCHGANGSKNOTEN

  (

  ID NUMBER CONSTRAINT NNC_STG_DURCHGANGSKNOTENv1_ID NOT NULL,

  Kilometrierung VARCHAR2 (20) CONSTRAINT NNC_STG_DURCHGANGSKNOTENv1_Kilometrierung NOT NULL,

  Letzte_Aenderung DATE CONSTRAINT NNC_STG_DURCHGANGSKNOTENv1_Letzte_Aenderung NOT NULL,

  Knotentyp VARCHAR2 (100) CONSTRAINT NNC_STG_DURCHGANGSKNOTENv1_Knotentyp NOT NULL,

  Name VARCHAR2 (100),

  BZ_Bezeichner VARCHAR2 (100),

  GUI_Bezeichner VARCHAR2 (100),

  Spurplanabschnitt_ID NUMBER NNC_STG_DURCHGANGSKNOTENv1_Spurplanabschnitt_ID CONSTRAINT NOT NULL,.

  XML_Document XMLTYPE

  );

  How can I avoid this? I like to just get something like this:

  CREATE TABLE STG_DURCHGANGSKNOTEN

  (

  IDENTIFICATION NUMBER NOT NULL,

  Kilometrierung VARCHAR2 (20) NOT NULL,

  Letzte_Aenderung DATE NOT NULL,

  Knotentyp VARCHAR2 (100) NOT NULL,

  Name VARCHAR2 (100),

  BZ_Bezeichner VARCHAR2 (100),

  GUI_Bezeichner VARCHAR2 (100),

  Spurplanabschnitt_ID NUMBER NOT NULL,

  XML_Document XMLTYPE

  );

  Thank you

  Matthias

  Hi Matthias,

  The NOT NULL Constraint clause appears likely because 'Not Null Constraint Name' property is set to the column.  (It is indicated on the Panel "forced by default and ' in the column properties dialog box.)

  To stop these products, you can go to the Data Modeler/DOF of the preferences page (on the Tools menu) and set the option 'generate short form of NO forced NULL.

  Note that there now is a forum specifically for the Data Modeler: SQL Developer Data Modeler

  David

• ON DELETE CASCADE and the CASCADE CONSTRAINTS - what are the difference?

  I know that CASCADE CONSTRAINTS would allow me to remove the parent key and the reference of the following children will be freed from the constraints. However, the child columns will remain and will be set to NULL.
  
  SO:
  
  If the CASCADE CONSTRAINTS could do the job, why do we need on REMOVE CONSTRAINTS?
  
  Unnecessary extra Note:
  
  I know that YOU DELETE CONSTRAINT is defined with the child. When I tried to delete the parent key without having the CONSTRAINTS of the WATERFALL, I got an error message indicates that the parent key has childs! So ON DELETE CASCADE was not up to what I had to mention the CASCADE CONSTRAINTS when deleting the parent key while the CASCADE CONSTRAINTS worked fine without ON DELETE CASCADE on the side of the child.
  
  I hope that my question is simple...

  A foreign key with a delete cascade means that if a record in the parent table is deleted, then the corresponding records in the child table with automatically deleted. This is a deletion of the waterfall.

  Forced to cascade deletes all foreign keys that reference the table to remove, and then deletes the table.

• Could not add the instance VO in the AM data model

  Jdev version: 11.1.2.4

  Steps to follow:

  (1) created a VO based on the SQL query.

  (2) when you try to add the VO instance in the AM data model, "Add an Instance" arrow (right arrow) is disabled.

  Please advise.

  Found resolution - Metalink Note 1530486.1.

• Not able to run the NVL function in the data model

  I tried to use NVL today in the data model, but I got the error message.
  Here's the code: -.
  SELECT ROUND (WHEN BOX: MO_TARGET_DISP_RATE > = 100)
  THEN 100
  (TO ANOTHER NVL (: MO_TARGET_DISP_RATE, 1) END, 2) AS "TARGET_PC_MO".
  
  Y at - it another option to replace NVL here... that runs in the NOSE? Thanks in advance.

  Just a suggestion, try a view then refer to the display in the data model

  (SELECT (ROUND (CASE WHEN to_number(:MO_TARGET_DISP_RATE) > = 100)))
  THEN 100
  Of OTHER NVL (to_number(:MO_TARGET_DISP_RATE), 1) END 2)), double) My_field

  The error was not a tank for the error number was or media...! If so above should be ok...

• I can create forms in the designer, but when I use a data model, I can't interact with the form

  In LiveCycle Designer ES2 I can create a form and then preview and interact with the form.

  This guess I just build objects by dragging the pieces pre-made object on the form (for example, text field) - which I can name, wrap in subforms something - I can add actions and all is well.  When I preview the PDF, I can enter data in the fields, click on the radio buttons, making things appear that everything is great.

  But LC ES2 is based on the data driven development model by, so in my case I need a form guide as well as the form - so it's better to have a model of data created in the first place - and then create the form based on the data model - then build guide form based on the data model - it is also a good idea, and I'm cool with that.

  My problem is that when I'm building a data model (just for a quick and dirty development demo, not associated with services back-end or databases) and I create the form based on the data model - I can't interact with all objects in the preview pane form - further when I launch the workspace and call my process that contains the form - I even can't interact with the form.

  What I am doing wrong?

  Summons - I can create a form and interact with it - but If I start with a data model and generate the form based on that - I can't interact with the form (option buttons click-I can not enter data in form fields - etc) what causes this?  What should I do to use a data model and be able to create an interactive form? >

  Does anyone know what causes this problem?  It's driving me crazy.

  Thank you-

  Ben

  You do not hurt anuthing. It works as advertised. When you generate a Guide and work with a fml data model designer you will only create a static non-fillable PDF file. This is because when you import the model in the designer of the model must be turned in a schema. The schema may not represent constraints and validations can be encoded in the model. The only thing that can be maintained is the structure, so Designer forbids you to buidl an interactive form.

  If you know what you're doing, you could take the data it is generated from the Guide and merge on a XDP template file that you create (unless he models in a first time - you can use the sample XML data as a starting point) using LC forms. Edowmside, is that if there are constraints and rules you would have to code them in the model as well. That's the way it is now there, but it will improve over time, as more of the ability of the model is exposed to the XFA world.

  Hope that helps

  Paul

• Add to the data model

  I know that you can add to a data model to help

  myDataModel.append(data)
  

  Is there an equivalent of the function to add data to the beggening of a data model?

  myDataModel.insert (0, data)

• -You also get an invalid identifier error when executing this query sql for a data model, but not in TOAD/SQL Developer?

  Hello OTN.

  I don't understand why my sql query will pass by in the data model of the BI Publisher. I created a new data model, chose the data source and type of Standard SQL = SQL. I tried several databases and all the same error in BI Publisher, but the application works well in TOAD / SQL Developer. So, I think it might be something with my case so I'm tender hand to you to try and let me know if you get the same result as me.

  The query is:

  SELECT to_char (to_date ('15-' |)) TO_CHAR(:P_MONTH) | » -'|| (To_char(:P_YEAR), "YYYY-DD-MONTH") - 90, "YYYYMM") as yrmth FROM DUAL

  
  

  Values of the variable:
  

  : P_MONTH = APRIL

  : P_YEAR = 2015

  I tried multiple variations and not had much luck. Here are the other options I've tried:

  WITH DATES AS

  (

  Select TO_NUMBER (decode (: P_MONTH, 'JANUARY', '01',))

  'FEBRUARY', '02',.

  'MARCH', '03'.

  'APRIL', '04'

  'MAY', '05'.

  'JUNE', '06'.

  'JULY', '07',.

  'AUGUST', '08'.

  'SEPTEMBER', '09'.

  'OCTOBER', '10',.

  'NOVEMBER', '11'.

  "DECEMBER", "12."

  '01')) as mth_nbr

  of the double

  )

  SELECT to_char (to_date ('15-' |)) MTH_NBR | » -'|| (TO_CHAR(:P_YEAR), 'DD-MM-YYYY') - 90, "YYYYMM")

  OF DATES

  SELECT to_char (to_date ('15-' |: P_MONTH |)) » -'|| ((: P_YEAR, 'MONTH-DD-YYYY')-90, "YYYYMM") as yrmth FROM DUAL

  I'm running out of ideas and I don't know why it does not work. If anyone has any suggestions or ideas, please let me know. I always mark answers correct and useful in my thread and I appreciate all your help.

  Best regards

  -Konrad

  So I thought to it. It seems that there is a bug/lag between the guest screen that appears when you enter SQL in the data model and parameter values, to at model/value data.

  Here's how I solved my problem.

  I have created a new data model and first created all my settings required in the data model (including the default values without quotes, i.e. APRIL instead "Of APRIL") and then saved.

  Then I stuck my sql query in the data model and when I clicked ok, I entered my string values in the message box with single quotes (i.e. "in APRIL' instead of APRIL)

  After entering the values of string with single quotes in the dialog box, I was able to retrieve the columns in the data model and save.

  In the data tab, is no longer, I had to enter the values in single quotes, but entered values normally instead, and the code worked.

  It seems the box prompted to bind the values of the variables when the SQL text in a data model expects strings to be wrapped in single quotes, but no where else. It's a big headache for me, but I'm glad that I solved it, and I hope this can be of help to other institutions.

  See you soon.

• Determinations of web OPA shows white screen when you use the data model

  Hello

  I use Oracle Policy Modeling 10.5.5.40 on windows 7. I use embedded apache tomcat to test.

  I have started a new project, added a simple rule:
  

  [b1] the parent is eligible for the benefits of compassion so

  [b2] parent has a child

  I chose 'Build and Run' selected web determinations, work very well.

  When I added a data model, created two entities, parent-child, and the child is contained in the parent as to-many, then ran the project, it won't work any more. The section that says:

  =====

  The screen automatic

  • Is the eligible parent to compassionate care benefits?

  =========

  is absent.

  I also tried to open an example of "MembershipDemo" that comes with OPM, same problem.

  Any ideas how can I fix?

  Thank you very much

  Looks like you have probably changed the Boolean value "the parent is eligible for compassionate care benefits" from the global to the parent. This means that is no longer a goal because it is a single Boolean value that can be determined, it is now a Boolean value for each parent in the rule template.

  The goal that presents itself as the first screen in your interview display all the high-level objectives - that is, all objectives at the global level.

  Some possible solutions to get a goal for your interview may are:

  1. If you try to determine cbb for 1 single parent, then you probably shouldn't introduce a parent entity, use the global as a parent

  2 introduce a global "all determined the eligibility of the BCC of parents" trying to see if "the parent is eligible for compassionate care benefits" is known to all parents

  3 decide which is the highest level (s) for your interview and to introduce these Boolean values to the global level.

• Developer reports 11g fails when opening the data model view

  Hello

  I see this on one of my client sites.

  They have just upgraded to 11.1.2.2.0 suite of developer on Windows 7.  The works of developer of fine forms, reports developer opens the report ok, but when you try to use the data model view, the program crashes and closes.

  I checked the usual suspects such as the REPORTS_TMP registry variable.

  This happens when trying to create a whole new report also, therefore seems to be an installation problem.

  Saw someone else this please?

  Tony

  Hello Tony,.

  Then, check this box.

  Hamid

• How to add an index to a materialized in Data Modeler 3.3 view

  Hi all

  I am looking for a step-by-step add an index on a materialized view in the 3.3.0.747 Data Modeler, as I couldn't find a way to do it so far.

  I looked here:

  Relational model

  Physical model

  Oracle 11g

  Materialized views

  'my_mv_name '.

  'INDEX' ARE NOT HERE IN the TREE

  "Tables" does not include either

  Thank you and best regards,

  Blama

  Hi Laurent,.

  You can create a Table with the same name and associate it with the materialized view (attributing to "Implement as Materialized View" in the properties of physical model for the Table.)

  If you configure columns and indexes on the Table, the Index will be included in the DDL generated for the materialized view.

  Kind regards

  David

• Group data model does not

  Hello

  I am developing a revision update for my app BB10 stunts and I use a data model to pull in the elements of the application do not forget; the only problem I encounter is that I can't get the data model of the group work so that I can arrange the items by the first character instead the data are currently presented as Z - A, even if I could get it to display in A - Z would be enough, but what I am looking to achieve is to get the model to display in A - Z and then sort by the first character, while a header for each letter is displayed.

  Here is the list (QML) and my data model (C++)

  ListView {
                              dataModel: _noteBook.model
  
                              listItemComponents: ListItemComponent {
                                  type: "item"
  
                                  StandardListItem {
                                      title: ListItemData.title
                                      description: ListItemData.status
                                  }
                              }
  
                              onTriggered: {
                                  clearSelection()
                                  select(indexPath)
  
                                  _noteBook.setCurrentNote(indexPath)
  
                                  _noteBook.viewNote();
                                  navigationPane.push(noteViewer.createObject())
                              }
                          }
  

  NoteBook.cpp

  #include "NoteBook.hpp"
  
  #include "NoteEditor.hpp"
  #include "NoteViewer.hpp"
  
  #include 
  
  using namespace bb::cascades;
  using namespace bb::pim::notebook;
  
  //! [0]
  NoteBook::NoteBook(QObject *parent)
      : QObject(parent)
      , m_notebookService(new NotebookService(this))
      , m_model(new GroupDataModel(this))
      , m_noteViewer(new NoteViewer(m_notebookService, this))
      , m_noteEditor(new NoteEditor(m_notebookService, this))
  {
      // First Character grouping in data model
      m_model->setGrouping(ItemGrouping::FirstChar);
  
      // Ensure to invoke the filterNotes() method whenever a note has been added, changed or removed
      bool ok = connect(m_notebookService, SIGNAL(notebookEntriesAdded(QList)), SLOT(filterNotes()));
      Q_ASSERT(ok);
      ok = connect(m_notebookService, SIGNAL(notebookEntriesUpdated(QList)), SLOT(filterNotes()));
      Q_ASSERT(ok);
      ok = connect(m_notebookService, SIGNAL(notebookEntriesDeleted(QList)), SLOT(filterNotes()));
      Q_ASSERT(ok);
  
      // Fill the data model with notes initially
      filterNotes();
  }
  //! [0]
  
  //! [1]
  void NoteBook::setCurrentNote(const QVariantList &indexPath)
  {
      // Extract the ID of the selected note from the model
      if (indexPath.isEmpty()) {
          m_currentNoteId = NotebookEntryId();
      } else {
          const QVariantMap entry = m_model->data(indexPath).toMap();
          m_currentNoteId = entry.value("noteId").value();
      }
  }
  //! [1]
  
  //! [2]
  void NoteBook::createNote()
  {
      // Prepare the note editor for creating a new note
      m_noteEditor->reset();
      m_noteEditor->setMode(NoteEditor::CreateMode);
  }
  //! [2]
  
  //! [3]
  void NoteBook::editNote()
  {
      // Prepare the note editor for editing the current note
      m_noteEditor->loadNote(m_currentNoteId);
      m_noteEditor->setMode(NoteEditor::EditMode);
  }
  //! [3]
  
  //! [4]
  void NoteBook::viewNote()
  {
      // Prepare the note viewer for displaying the current note
      m_noteViewer->setNoteId(m_currentNoteId);
  }
  //! [4]
  
  //! [5]
  void NoteBook::deleteNote()
  {
      m_notebookService->deleteNotebookEntry(m_currentNoteId);
  }
  //! [5]
  
  bb::cascades::GroupDataModel* NoteBook::model() const
  {
      return m_model;
  }
  
  QString NoteBook::filter() const
  {
      return m_filter;
  }
  
  //! [6]
  void NoteBook::setFilter(const QString &filter)
  {
      if (m_filter == filter)
          return;
  
      m_filter = filter;
      emit filterChanged();
  
      // Update the model now that the filter criterion has changed
      filterNotes();
  }
  //! [6]
  
  NoteViewer* NoteBook::noteViewer() const
  {
      return m_noteViewer;
  }
  
  NoteEditor* NoteBook::noteEditor() const
  {
      return m_noteEditor;
  }
  
  //! [7]
  void NoteBook::filterNotes()
  {
      NotebookEntryFilter filter;
  
      // Use the entered filter string as search string
      filter.setSearchString(m_filter);
  
      const QList notes = m_notebookService->notebookEntries(filter);
  
      // Clear the old note information from the model
      m_model->clear();
  
      // Iterate over the list of notes
      foreach (const NotebookEntry ¬e, notes) {
          // Copy the data into a model entry
          QVariantMap entry;
          entry["noteId"] = QVariant::fromValue(note.id());
          entry["title"] = note.title();
          entry["status"] = NoteViewer::statusToString(note.status());
  
          // Add the entry to the model
          m_model->insert(entry);
      }
  }
  //! [7]
  

  NoteBook.hpp

  /* Copyright (c) 2012, 2013  BlackBerry Limited.
  *
  * Licensed under the Apache License, Version 2.0 (the "License");
  * you may not use this file except in compliance with the License.
  * You may obtain a copy of the License at
  *
  * http://www.apache.org/licenses/LICENSE-2.0
  *
  * Unless required by applicable law or agreed to in writing, software
  * distributed under the License is distributed on an "AS IS" BASIS,
  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  * See the License for the specific language governing permissions and
  * limitations under the License.
  */
  
  #ifndef NOTEBOOK_HPP
  #define NOTEBOOK_HPP
  
  #include 
  #include 
  #include 
  
  #include 
  
  class NoteEditor;
  class NoteViewer;
  
  /**
   * @short The controller class that makes access to notes available to the UI.
   */
  //! [0]
  class NoteBook : public QObject
  {
      Q_OBJECT
  
      // The model that provides the filtered list of notes
      Q_PROPERTY(bb::cascades::GroupDataModel *model READ model CONSTANT);
  
      // The pattern to filter the list of notes
      Q_PROPERTY(QString filter READ filter WRITE setFilter NOTIFY filterChanged);
  
      // The viewer object for the current note
      Q_PROPERTY(NoteViewer* noteViewer READ noteViewer CONSTANT);
  
      // The editor object for the current note
      Q_PROPERTY(NoteEditor* noteEditor READ noteEditor CONSTANT);
  
  public:
      NoteBook(QObject *parent = 0);
  
  public Q_SLOTS:
      /**
       * Marks the note with the given @p indexPath as current.
       */
      void setCurrentNote(const QVariantList &indexPath);
  
      /**
       * Prepares the note editor to create a new note.
       */
      void createNote();
  
      /**
       * Prepares the note editor to edit the current note.
       */
      void editNote();
  
      /**
       * Prepares the note viewer to display the current note.
       */
      void viewNote();
  
      /**
       * Deletes the current note.
       */
      void deleteNote();
  
  Q_SIGNALS:
      // The change notification signal for the property
      void filterChanged();
  
  private Q_SLOTS:
      // Filters the notes in the model according to the filter property
      void filterNotes();
  
  private:
      // The accessor methods of the properties
      bb::cascades::GroupDataModel* model() const;
      QString filter() const;
      void setFilter(const QString &filter);
      NoteViewer* noteViewer() const;
      NoteEditor* noteEditor() const;
  
      // The central object to access the notebook service
      bb::pim::notebook::NotebookService* m_notebookService;
  
      // The property values
      bb::cascades::GroupDataModel* m_model;
      QString m_filter;
  
      // The controller object for viewing a note
      NoteViewer* m_noteViewer;
  
      // The controller object for editing a note
      NoteEditor* m_noteEditor;
  
      // The ID of the current note
      bb::pim::notebook::NotebookEntryId m_currentNoteId;
  };
  //! [0]
  
  #endif
  

  If something you can help me with then this would be very useful - if you need to see more of code then let me know too!

  Thanks in advance

  Try to add in constructor (after a call to setGrouping):

  QStringList keys;
  key<>
  m_model-> setSortingKeys (keys);

  May require alterations, I have not tried this compilation.

• Export file DDL in SQL Developer Data Modeler

  I export my last project of relational model of the DDL weeks in hopes of getting a quick and precise way to create my 17 tables. In the relational model, Cust_ID is the PK yet there is nothing indicating it in the script that is created from the export file DDL.  That's what he created.  Now, when I right click on the customer table in the view of the relational model and then choose Preview DDL, it adds the line of alter table. But when I do this for most of the opther whose phones table tables in the image below, it's just the fields, no PK or PK info. How can I get the PK and FK stand? Thank you, Peter

  CREATE THE customer TABLE

  (

  Cust_id INTEGER NOT NULL,

  Name VARCHAR2 (128).

  Address VARCHAR2 (128 CHAR)

  ) ;

  ALTER TABLE customer ADD CONSTRAINT Customer_PK PRIMARY KEY (Cust_ID);     <-this is displayed in the preview of the DOF, not export file DDL. The telephone table does not show the constraints or keys in each view. Even with almost all tables.

  That's what I have for phones

  CREATE TABLE phones

  (

  Phone_ID INTEGER NOT NULL,

  Phone_Type NVARCHAR2 (10),

  Phone_Number TANK (14),

  Customer_Cust_ID INTEGER NOT NULL

  ) ;

  

  Hi Peter,.

  A couple of points to check for definitions of key primary and missing foreign key:

  1. the relational model for the primary keys and foreign keys dialogs have both checkboxes 'Generate in DDL', which are normally set.  Make sure they are always defined.

  2. When you make a DDL generation, on the generation of DDL Options screen, select the PK tabs and UK and foreign key constraints and check the boxes 'Selected' for relevant pharmacokinetics and the FKs are defined.  (These settings are remembered from one generation of DDL to the other, and an overview of the DDL will normally use the same parameters as the most recent generation of DDL).

  What Data Modeler version do you use?

  David

• Get a NAMED check constraint when the entity attribute derived from the field

  I'm designing a new database and beginning with a logic model of the ER. I've defined several areas, such as the NO_YES field (with values of ' no and 'Y'). When I use this area as a data type of an attribute of the entity (for example, the CHANGE_REQUEST.IS_APPROVED attribute), I also specify a constraint name (for example, CR_APPROVED_CK) of the attribute (this is done in the Group of constraint, property name constraint and the properties of the attribute dialog box, default value).
  
  When I have the logic model to a relational model of the engineer, the constraint name is lost. Specifically, for the definition of the table that is created, for the column in question, in the default column properties and constraints Panel dialog box, the name of constraint property is empty. When I generated the DDL of the relational model, the check constraint that is generated is an inline check constraint (such as ' IS_APPROVED VARCHAR2 (1) CHECK (IS_APPROVED IN ('n', 'Y')) '). When this DDL is executed to generate database objects, the created check constraint has a system-generated name. I want the constraint to have a name that I create.
  
  By experimentation, I found that in the relational model, if I specify a value for the property name of the constraint in the DOF resulting constraint get named (an ALTER TABLE statement is generated that contains "ADD CONSTRAINT CR_APPROVED_CK CHECK (IS_APPROVED IN ('n', 'Y'))"). However, I have redundantly change the relational model in the same way that I edited the logic model to specify the constraint names.
  
  Is there a way to guarantee that the constraint names defined in a logic model transferred during the engineering of a logic model to a physical model.
  
  The version of the Data Modeler I use is 3.0.0.665.

  Is there a way to guarantee that the constraint names defined in a logic model transferred during the engineering of a logic model to a physical model.

  There is ' compare/copy options' tab in the technical dialogue - clear the checkbox "do not apply to new objects.

  Philippe

• [SOLVED] Export Oracle SQL Data Modeler is missing a PRIMARY KEY on the DDL script

  I use data 4.1.888 maker to create an ER diagram and generate a DDL her script.

  The diagram contains more than 40 paintings, most of them have a primary key defined.

  For some reason any there is a table that has a primary key defined, but which is ignored when I export the model to a DDL script.

  It is the "wrong" key (even if it is checked that it is not found on the generated DDL script):

  

  This is where the key is set:

  

  And it is the preview of the DDL (Yes, primary key up there shows):

  

  This is what happens if I try to generate the DDL for just this (still not generated primary key) table:

  

  Has anyone had the same problem? Any ideas on how to solve it?

  There is no error in the log file, but when I run the generated DDL script there, and then I realized that I was doing something wrong:

  The table MEMBERS had a mandatory foreign key from another table, which in turn had a mandatory key against MEMBERS himself.

  So even if I could generate this primary key on members myself, and then run the the constraint definition that returned an error on the DDL script, I could not perform an insert operation on any of these two tables because of the constraint.

  I revised my design and realized relationships was not mandatory. I unchecked the mandatory box on the definition of the constraint and everything went well.

  I could reproduce the problem and the solution on a diagram with only two tables, so I'm sure that's it.

  Anyway, the Data Modeler is "a failed" silently in this kind of situation. It should be fairly obvious to an experienced designer that I was doing something wrong, but it is not so obvious when you deal with dozens of tables and all their relations and this is your first time using the Modeler.

  Thanks for your reply :-)