Version controlled packages in DBMS projects

[DanG83616]

I moved to the Corporate edition to make it easier for a team to work on a project. We had been using the Pro edition with all packages set for version control loaded into private projects. With the Copr edition I expected to use Get Package to load shared models into a DBMS project, check them out and then the whole team could use user locks at the element level. This would be the best of both worlds, shared packages under version control AND the ability for serveral teammates to work on the same package simulatiniously.

What actually happens is that EA notices the package is under external version control will allow only one user to edit a checked-out package. Does anyone know how I can get what want? That is, be able to check out the package and manage user locks on at the item level.

This situation isn't ideal but it is still better than everyone having a private model. At least changes are still seen by everyone as they happen.

Thanks,
Dan

[analia]

Version 6.5 (Build 803) works as you need: it allows the team to work on the same version controlled package and manages concurrency on element lock basis.
We are now trying to upgrade to Version 7.5 (Build 847) and we are having the problem you describe. If someone can help...

Thanks in advance.
Analia