We are using StrataFrame in a team environment and occasionally have had issues with multiple people accessing the DDT at the same time. Is there any locking or read-only feature available? If not, any ideas?



Thanks,

Derek

Why type of issue?  We use it in a team environment as well, so I am unaware of any issues in that regard.

We generally try to run the DDT against a local db on our dev machines, while the main db (where the actual StrataFrame db is stored) is the golden one that our automated builds run against. We try to limit any DDT changes - table modifications, etc. - that would cause compile errors after BO re-mapping and check-in to a single developer at a time. We instant message the dev group when we want to make DDT changes and then message again when done. Most of the time this works, but it would be nice if there was a locking/read-only mechanism that would prevent someone from editing the DDT while someone else already is.



Derek

I still don't understand the error or problem.  I understand what you are wanting, which may be a good idea.  But the problem I am having trouble understanding is that when you repackage the DDT profile for a deployment, it regathers from the server, so if you and someone else had both made changes it would get them both.

So basically, you don't want anyone else to modify the profile at all until you "unlock" it rfrom modification.  Correct?

That's correct. We generally try to not have multiple people in the DDT at the same time just so we can control when someone has to run the updated DDT against their databases. We want to make sure that all changes have been tested carefully, otherwise it can really mess up the team flow.



Thanks,

Derek