Can't check vi into source code control

[Jim77215]

We had a co-worker make numerous changes to a vi the other day. There is one problem, he forgot to check the vi out of source code control before he made his changes. I now need to somehow get this updated vi into SCC but SCC is refusing to take it. I know the proper procedure is to check the vi out first, make changes, then check it back in, but we just didn't do that in this case. Is there any kind of workaround for getting source code control to accept this updated vi?

[NeilR]

Hi Jim

I'm not sure which SCC you're using but I believe there are a couple of ways if you are using Visual SourceSafe.

You can check out the file but make sure you tick the "Don't get local copy" tickbox. In this way the changes that you have made will not be overwritten. Then check it back in with the updates.
Or ... you can take a copy of the updated file and put it somewhere safe. Check out the file in which case it will overwrite the changes. Then copy the updated file from the safe area back and overwrite the checked out file. Then check in the file complete with updates.

Whatever you do I would suggest you keep a copy somewhere safe, just in case. 🙂