I've seen this too. Its unfortunately Source Safe that is the problem. Basically, if I had the $/com/syntegra tree labelled to 1.3 and not the root $/com, when I tried to check out from source safe with the 1.3 label on the root, it doesn't know of any 1.3 label. From past experience, CVS was much better at this and recursed through until it found the label.
If you have items in the $/MKTG that are labelled up as 2.0 but not the actual root $/MKTG then it will never find those changed files. In Source Safe, labels recurse downwards. If the root is unaware of the label then you will get this error. Your choices are to either perform branching and pinning of the Source Safe tree for that version or version the root. This involves creating a new tree just for 2.0. Peter ******************************************************************** This email may contain information which is privileged or confidential. If you are not the intended recipient of this email, please notify the sender immediately and delete it without reading, copying, storing, forwarding or disclosing its contents to any other person Thank you Check us out at http://www.syntegra.com ******************************************************************** -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
