Moving <<table>>'s between diagrams

[AlexPeake]

I am learning about the Database capabilities. I added four tables with FK associations to Logical View | Logical Model. I tried to move these to Logical View | Data Model.

In the Project View, they appear to be in the Data Model, yet double clicking on the Data Model diagram shows an empty diagram. Double clicking on the (apparently) empty Logical View diagram shows the tables and associations.

Decidedly non-intuitive. What am I missing? (There appears to be nothing in Help about this?)

Alex

[Bruno.Cossi]

There is a difference between where (i.e. in which PACKAGE) are the tables (or any other objects for that matter) located (in your case DATA MODEL) and what diagrams they appear on.
Every object is stored in one package. It can however appear in more than one diagram, and the diagram itself may be located in different package.
So, in your case, you have tables stored in package "Data Model", diagram stored in "Logical Model", but the diagram displays the tables. You could easily either move the diagram as well, or create a new diagram and just drag and drop the tablkes on it.
Think of the diagram as a "page" or better as a "sub-model" or "sub-diagram" in typical data modeling tools.

Makes sense?

Bruno

[AlexPeake]

Thanks Bruno.

I am still somewhat confused by the realationship between the "Project View" and the "Diagram".

I started, as before, with the  tables on the "Logical Model" diagram. I moved the Logical Model diagram up under the Data Model folder (under the Data Model" diagram. In the Project View the tables remain under the Logical Model folder; they did not follow the diagram.

It appears that there is no realtionship between the Project View and the Diagrams?

[Bruno.Cossi]

Here is something that might help to clarify it a little bit... switch on "Highlight Foreign Object" feature (go to menu Diagram > Properties and check the checkbox Highlight Foreign Objects"). Underneath each table a text will appear, indicating which package is the table stored on. Try to move the tables around now, you will see that the text on the diagram will change to indicate the table's new location.
What this means is, the diagram can display tables (or any other objects) regardless of where they are located. One diagram can display objects from several different packages as well.
You might, for example, have one package where you would store all Actors, another one with all Use Cases (not that I would recommend structure like that). You could then have a diagram, stored in a thrid package, that would display both the Actors and the Use Cases together.
Packages are used to merely store the objects, whereas the diagrams display them in the fashion you want.

Bruno

[CJ]

G'day Alex,

Use the "Project View" (aka Project Browser) to browse all your elements, element properties, and diagrams (organized in any number of packages).  The Project Browser does not show any relationships between diagrams and elements.

Elements may appear in any number of diagrams (or may even appear in zero diagrams!).  Elements exist in your project totally independent of any diagrams they may appear in.

Use diagrams to visualize elements and relationships between elements.  The diagram view shows the currently selected diagram.  You can have any number of diagrams in any package in your project, showing elements from any package in your project.

(By the way, elements created by dropping them onto a diagram get stored in the same package as the diagram.  The element can be moved into another package after creation.  Elements dragged from the Project Browser to a diagram are not new elements ... just visual instances of a previously created element stored in the project and visible in the Project Browser.  Boys, I don't think I explained that all that well ...)

What do you mean by a "relationship between the Project View and the Diagrams"?  What kind of relationship are you expecting?  Is EA doing something different from other tools you've worked with?