467,887 Members | 1,539 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 467,887 developers. It's quick & easy.

Source Control Recommendation Wanted

We're currently using StarTeam 5.3 and are very p1ssed off with it. The
situation we have is this:

1 project in StarTeam with 2 views serving 2 Access projects. About 99%
of objects are common to both Access projects, about 2 or 3 objects
branched.

Equiv in VSS would be 2 VSS projects and 99% shared objects between
them.

Now if we're in Access project A, check out an object then open up
Access project B we get conflict messages and after a while we cannot
track where the object was really checked out to so it gets confusing.
We could write down this info as we go but I do believe this should be
a function of the source control package (to actually control it, not
get confused by it)

So what we need from a source control package is all the usual features
(check out/in, lock, change history, etc), to be client server driven
and work through a TCP/IP port for remote development and not get its
knickers in a twist.

Source Safe is not an option, it's not C/S, the file based nature rules
it out for remote development.

Any suggestions?

Nov 13 '05 #1
  • viewed: 956
Share:

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

6 posts views Thread by democratix | last post: by
4 posts views Thread by AMP | last post: by
3 posts views Thread by Brenden Bixler | last post: by
2 posts views Thread by =?Utf-8?B?ZWxpYXNzYWw=?= | last post: by
reply views Thread by MrMoon | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.