Single Shared Model for version control.

[pH]

Hi All,

I am not very clear what Single Shared Model means for version control.
Is it as simple as EAP file stored on network drive?

If thats true then how can it be used for version control
because configuring for version control required local working directory path? Does it mean the local working copy must also reside on the machine where EAP fileis stored ?

Thanks,
pH

[Geert Bellekens]

Yes it is as simple as that.
I think it uses a "real" local path on the clients machine to store the versioned xmi files.
I would not recommend that approach however given the reputation of MS Access and multiple users.
Setting up a real database can't be that hard or costly. There are a few supported databases that you can use for free.

Geert

[pH]

Thanks.

I tried to set up the model in db repository. It was pretty easy and straight forward.

Is Single shared model stored in DBMS preferred over multiple private models for version control?

Thanks again.
pH

[Geert Bellekens]

I would think so, unless you have users in seperate remote locations.
The database connection over a WAN can get pretty slow, so in that case you are better of with multiple private models.