File Status

In most cases, the status of your files in StarTeam determines the operations that you can perform on them. The following table lists all file statuses and presents a description of each status.

Missing: The file is part of the project view, but it is not in your working folder. If you want to place the file into a working folder on your hard drive, you must check this file out.
Merge: The working file has been altered but is not based on the tip revision (most recent revision) of this file. This status usually appears when you and another team member work on a file at the same time, but the other person checks the file in before you do. When you check this file in, the application prompts you to merge your file with the tip revision.
Modified: The working file has been altered and is based on the tip revision of this file. You may want to check this file in so that the changes are placed in the application.
Out of Date: The working file is a copy of a prior revision of the file. If you need the tip revision, you should check it out.
Not in View: The file is in your working folder but not in the project view. You may want to add this file to the view. If you are no longer using the file, you may want to delete it from the working folder.
Current: The tip revision of this file is in the working folder.
Unknown: The file in the working folder has the same name as a file in the view, but it was not checked out from the repository. You may have copied it from another location. Use Update Status to determine the correct status.

During the file check-out process, the Integration copies a file revision from the repository to a working folder. Checking in a file places a new revision in the repository. In many cases, the status of a file affects the check in or check out process.

The following table summarizes the relationship between file status and the check-in and check out operations for the application. A successful check in or check out operation changes the status of your working file to Current, unless you have checked out a historical revision or deleted the working file as part of the operation.

Status	Check In	Check Out
Current	No considerations.	No considerations.
Merge	Starts the merge utility unless you force the check in. File Compare/ Merge, the default merge utility, enables you to merge text files. Merge status means that someone else has checked in this file after your last check out. You do not have their changes in your working file. As a result, their changes will be lost unless the files are merged.	Not allowed unless you force the check out. Your changes will be lost if you check out this file.
Missing	Not applicable. If a file has Missing status, it is not in your working folder so nothing can be checked in.	If a file has Missing status, the application asks whether you want to check it out when you open it. You can also check it out manually.
Modified	No considerations. Unless someone else has the file locked, you can check in the file.	Not allowed unless you force the check out. Your changes will be lost if you check out this file because it overwrites the file in your working folder.
Not in View	Not applicable. A file with Not in View status cannot be checked in. You can add it to the project with the Add Files command.	Not applicable. A file with Not in View status is not in the repository, so nothing can be checked out.
Out of Date	Not allowed unless you force the check in. If you check in an Out Of Date file, that the tip revision will no longer have the changes made to the file after your working copy became Out Of Date.	No considerations. Checking out an Out Of Date file makes your working file Current.
Unknown	Not allowed unless you force the check in. Checking in your working file makes it the tip revision in the repository. If the file status is Unknown, the consequences of this action are also unknown. Use Update Status with an MD5 checksum to see if the file can be identified. If the file cannot be identified, you may want to compare your working file to the tip revision.	Not allowed unless you force the check out. Performing a check out overwrites your working file with the tip revision in the repository. If a file’s status is Unknown, the consequences of this action are also unknown. Use Update Status with an MD5 checksum to see if the file can be identified. If the file cannot be identified, you may want to compare your working file to the tip revision.