Projects x Models

[Tomas Klicka]

Hi.

I need a help (maybe advice). I've bought EA some 3-4 years ago in Desktop Edition and from time to time I created a diagram. Now I've bought upgrade to Corporate Edition, because I wanted to work on multiple projects not each in eap file separately, but all of them in DBMS - one model (or project - see later) as framework and other models are using classes from this framework.

And now I've got a problem - I thought, I could create Project (not Model) Framework and then next Project (let's say Project1) and use classes from Framework as "externals" (I worked a while with SCA, where they used this and I liked it). And the same with Project2 and so on.

But I didn't find a way how to realise this (I'm using MS SQL) - I found the only way how to realise something such via a Models in one Project (database), but I don't like this way very much.

Is there any posibility how to work with Projects instead of Models?

Thank for any help.

(I hope I wrote it intelligible

[Geert Bellekens]

Please define the difference between Project and Model...

As I see it neither are used in the context of EA.
There are Repositories and Root Nodes, and that's about it.
I don't think there's a difference between use .eap files or a database in that respect.

Geert

[Tomas Klicka]

Thanx for your reply. I'll try to explain my thoughts.
Till now I had every one Project in one separate eap file. It wasn't able to have common part - framework - in one eap file and then reference classes from this file in other files (projects).
I hoped that it would be possible to have (when I upgrade to higher version EA and use MS SQL server): framework in one database and projects in other databases and I could reference or subclass classes in the other databases with projects into the database with framework.
I know I can have multiple root nodes (models) in one database, but I don't want to have mixed multiple different project in one "tree" (if it is possible).
Thanks for your help.

[qwerty]

The answer is simple: that's not possible. You need to place everything in one schema under different roots. In order to make cross references between different projects use EA security to lock parts (from an admin account so nobody can change its).

q.

[Tomas Klicka]

OK. That's the final info I needed to start planning my work. Thank you very much :-)