Ok, fair enough. How to handle making sure that we can work on new development (projects) and also bug fixes to production when they both share the same code? Right now, I have some processes in place where I keep things local in a project (backed-up and archived of course) and only check them all back in when they are close to release. The other guy does it similar to me, though not near as retentive in making sure that the files are in sync. Things like binary files, especially the project always have to be manually figured out. Also, it's just hard because the codeset you started with back a few months ago has changed due to production fixes and now you have to merge everything all over again Seems like there has to be a better way of doing it.


>Branching... scary, scary stuff. And not just in Vault. The biggest problem you'll have with VFP is that you have binary source files (ie forms, class libs, reports, etc) that just don't get put back together. My advice, avoid branching all together.
>
>
>>I should not be restricted in the forums I post in just because I don't want to subscribe to them and see all their messages. I should be able to post in whatever forum then I can read in the "Get all the replies to your messages" area if anyone responds to me.
>>
>>That said...
>>
>>What is the easiest way to branch projects in Vault? We have a couple projects, but in our production version we tend to step on each other's toes and I'm basically tired of having to reconcile stuff all the time. How does branching really work - not looking for the SourceGear explanation really, just the layman's version.