How to upgrade files in one Vault folder to a new version?

[Perry]

(First time I tried to post this, I got this error: "The forum you selected does not exist." I guess there must be a bug in the forum code, but, of course I didn't know that when I started this post, so that is not my topic.)

I have one subfolder in Vault, which holds a bunch of files which come from another project (a big project using some distributed management system). Now, a new version of those files is released, and I go and download the new version (via whatever -- maybe subversion, or cvs, or someone emails me the new version -- that is outside the scope of this).

So, now I have the new version locally, and I need to check in the new version to the version in Vault. How do I do it?

Obviously I want to check out the folder, then delete all the old ones, and put in all the new ones (many of which have the same names -- there might be some old ones that disappear, and some new ones that appear).

I realize this is a very simple thing, but, would anyone mind telling me just how to do it with SourceGear Vault?

I looked in the Vault Client help, and there is a section
Using Vault
Working with Folders
Check Out and Check In Folders

but it just says to check out the folder, then check it in.

I know from my own experience with Vault that it will not add the new files -- at least not with the default options -- are there options that I need to change to make it work correctly here?

[lbauer]

One suggestion -- check out the folder, delete the files in the working folder, then replace them with all the new files. Files with the same names will have a status of Edited. Check in the folder. Files with "missing status" may still be checked out, so undo checkout with the "leave" or "delete" option.

Files with the status missing (old files) are in the repository but no longer in the working directory. These can be deleted or moved if they are no longer needed. You can do a status search for "missing" on the parent folder to list them all.

To add the new files, select the parent folder, right click ->Detect new files to add to add the new files.

[Perry]

(I got several of these errors again: You must select a topic to reply to)

Thank you for the procedure, but, that looks rather cumbersome, and perhaps more problematically, won't that lead to the changes being scattered across different check-ins? Shouldn't all the changes be checked in as one atomic unit, all sharing one check-in comment, so there aren't any broken intermediate steps?

[lbauer]

Yeah, it isn't very elegant. Maybe someone will chime in with a better idea.

But you should be able to commit everything as one change set as long as auto-commit is off and you undo the checkout on the missing files before you commit.