By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,492 Members | 1,289 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,492 IT Pros & Developers. It's quick & easy.

Source Control Recommendation Wanted

P: n/a
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
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.