Copyright: Copyright© 1992-1996 Microsoft Corp.  All rights reserved.
Citation: Copyright© 1992-1996 Microsoft Corp.  All rights reserved.


Glossary

A

access rights

Advanced dialog box

automatic merge

B

branched file

branching

C

checked-in file

checked-out file

check out folder

cloaking

column format

conflict

conflict marker

cross-platform development

current project

current version

D [image] F

delta

Delete command

Destroy command

development environment

drag and drop

file header

file list

file pane

G [image] K

inheritance

history

keyword

keyword enabled file

keyword expansion

L

label

local copy

locking

log on

M

master copy

merging

multiple check out

N [image] Q

parent project

password

project

project list

project pane

Purge command

R

read-only file

recursive operation

reverse delta

rights propagation

root project

Results pane

S

security

shadow folder

shadow variable

shared file

share link

source code control

status bar

subproject

T [image] V

user list

username

version control

version number

version tracking

Visual merge

Visual SourceSafe administrator

Visual SourceSafe database

Visual SourceSafe Explorer

W [image] Z

web site project

wildcard characters

working folder


user list <definition>
user list

The list of users who can use the Visual SourceSafe database.  This list is maintained by the Visual SourceSafe administrator and displayed in Visual SourceSafe Administrator's main window.


access rights <definition>
access rights

The levels of permission to use the Visual SourceSafe database that users are granted by the Visual SourceSafe administrator when project security is enabled.  The levels of access rights are Read, Check Out, Add, and Destroy.  For more information, see the Administration chapter of the Microsoft Visual SourceSafe User's Guide.


Advanced dialog box <definition>
Advanced dialog box

A dialog box that contains optional or additional settings.  Many SourceSafe dialog boxes have an Advanced button that displays these additional settings.


automatic merge <definition>
automatic merge

When multiple users have the same file checked out, their changes to the file are merged by Visual SourceSafe during check in.


branched file <definition>
branched file

A file whose share link has been broken using the Branch command.


branching <definition>
branching

The process of sharing a file with another project and then separating it into two (or more) branches.  Branching creates two paths of the file's history, both with a common version as the origin, but different subsequent versions.


checked-in file <definition>
checked-in file

A file stored in the Visual SourceSafe database and unavailable for modification.


checked-out file <definition>
checked-out file

A file that has been reserved for work by a user.  Users check out files so changes can be made to them.  In the default configuration, Visual SourceSafe allows only one user at a time to check out a file.  Checking out a file copies its latest version into the user's working folder.


check out folder <definition>
check out folder

The folder to which a file is checked out in Visual SourceSafe.  It is important to distinguish this from the working folder.  If you check out a file, the file is checked out to your working folder.  From the perspective of another user, the file is in the check out folder.  The check out folder is displayed in the Check Out Folder column of the file pane of Visual SourceSafe Explorer; the working folder is displayed under the toolbar.


Clipboard <definition>
Clipboard

A temporary storage location used by Microsoft Windows to transfer text, graphics, and code.


cloaking <definition>
cloaking

Hiding a project from being affected by certain commands, namely Get, Check Out, Check In, Undo Check Out, and Project Show Difference.


columnar formatting <definition>
column format

A formatting option used with keyword expansion within a file.  This option (using two colons instead of one in the keyword instructions) tells Visual SourceSafe to align columns of keyword information for a more attractive and readable display.


conflict <definition>
conflict

Two or more differing changes to the same line of code in a multiple check out situation.  Visual SourceSafe recognizes conflicts during a merge operation, either explicitly when a user clicks the Merge Branches command, or implicitly when checking in a file that multiple users have checked out.


conflict marker <definition>
conflict marker

A symbol used to designate conflicting changes to a file.  These symbols are:

   <<<<<<   SourceSafe version

   ======   Conflict separator

   >>>>>>   Local version

Visual SourceSafe places these markers in the file after a conflicting check-in or merge operation, so that you can find and resolve the conflict more easily.


cross-platform development <definition>
cross-platform development

Visual SourceSafe supports transparent file-compatibility across multiple processors and operating systems.


current project <definition>
current project

The project selected in the project pane of the Visual SourceSafe Explorer window.


current version <definition>
current version

The version of a file most recently stored in the Visual SourceSafe database.  The current version has the highest version number of a file in Visual SourceSafe.


delta <definition>
delta

Changes. In Visual SourceSafe, a delta is the difference between version X of a file and version X [image] 1 of the same file. Visual SourceSafe uses reverse delta technology to store changes.


Delete command <definition>
Delete command

Removes files and projects from a Visual SourceSafe project, and marks them as deleted; the items still exist, however, and can be recovered using the Recover command.


Destroy command <definition>
Destroy command

Permanently removes deleted files and projects from the Visual SourceSafe database.  Once destroyed, the items cannot be recovered.


development environment <definition>
development environment

A set of software development tools, presented as a unified environment in which the software developer can efficiently work.  Microsoft Visual Basic and Microsoft Visual C++ are examples of such environments, as they combine a coding language with tools and controls.  Visual SourceSafe can be integrated into these environments, providing access to its source code control features.


drag and drop <definition>
drag and drop

A combination of features that allows the user to drag an item and drop it onto another item using the mouse.  An item can be a source (the item the user drags) or a target (the item on which the user drops a source).

To drag an object, click the object, then while holding down the mouse button, move it to the new location.  Release the mouse button to drop the object.


file header <definition>
file header

Text at the beginning of a file that contains information, such as the revision number of the file, the author, the date and time of last modification, and so forth.  So it doesn't interfere with compiling, this information usually appears as comments in programming language files.


file pane <definition>
file pane

The right side of the Visual SourceSafe Explorer window.  This pane contains the file list, a list of all the files in the current project.


file list <definition>
file list

The list of files in the current project, found in the file pane of the Visual SourceSafe Explorer window.


history <definition>
history

A record of changes to a file since it was initially added to Visual SourceSafe, which Visual SourceSafe keeps by using reverse delta technology.  With the file history, you can return to any point in the file's history and recover the file as it existed at that point.  The History of Project dialog box shows the record of significant events in the current project, such as labeling, and deletion or addition of files and subprojects.


inheritance <definition>
inheritance

The inherited effect of variables in Visual SourceSafe initialization files that subprojects receive from their parent projects.  Variables in these files can be grouped under headings to specify behavior.  If a variable is set before any group heading in the initialization file, the variable affects all projects; the effect is inherited by the subproject variables.


keyword <definition>
keyword

A word with a special meaning to Visual SourceSafe.  You can use keywords in your text files to automatically create a file header with version-specific information.  Use Visual SourceSafe keywords to place information from Visual SourceSafe directly into a text file.


keyword enabled file <definition>
keyword enabled file

A file that contains Visual SourceSafe keyword information.


keyword expansion <definition>
keyword expansion

The process Visual SourceSafe uses to replace a Visual SourceSafe keyword with meaningful header information when you use the Check In and Add Files commands.  For example, the string "$Revision:   $" tells Visual SourceSafe to expand the Revision keyword automatically with the current file version number.


label <definition>
label

A user-defined name you can attach to a specific version number of a file or project.


local copy <definition>
local copy

A copy of a file stored in your working folder on your local computer.  The local copy may differ from the Visual SourceSafe master copy if the local copy has been changed since the last check out, or if the master copy was changed by another user while you were working on the local copy.


locking <definition>
locking

A system of ensuring that two processes do not try to affect the same record in a database at the same time.  To coordinate record access, Visual SourceSafe applies native locking, which uses native operating system functions.  Visual SourceSafe also can be set to use lockfiles, which create temporary files in the LOCKS folder.


log on <definition>
log on

The process of entering and verifying a user's name and password to access the Visual SourceSafe database.


master copy <definition>
master copy

The most recently checked-in version of a file stored in the Visual SourceSafe database, as opposed to the local copy of a file in your working folder.


merging <definition>
merging

The process of combining differences in two or more changed copies of a file into a new version of the file.  A merge involves at least two different files (which may be different versions of the same file or changes made to the same version of the file) and creates a new file made up of the results of the merge.


multiple check out <definition>
multiple check out

Simultaneous check outs by two or more users.  Multiple check out is not possible unless it is enabled by the Visual SourceSafe administrator.


parent project <definition>
parent project

A project that contains one or more subprojects.  A project can be both a parent project and a subproject at once, if it is in the middle of the project hierarchy.


password <definition>
password

A text string used as security to verify the identity of a user.  A user password is often required to use the Visual SourceSafe database.


project <definition>
project

A group of related files, typically all the files required to develop a software component.  Files can be grouped within a project to create subprojects.  Projects can be defined in any way meaningful to the user(s) [image] as one project per version, or one project per language, for example.  In general use, projects tend to be organized in the same way file directories are.


project pane <definition>
project pane

The left side of the Visual SourceSafe Explorer window.  The project pane contains the project list, a list of all available projects in the Visual SourceSafe database.


project list <definition>
project list

A list, in the left pane of the Visual SourceSafe Explorer window, of all the projects available in the Visual SourceSafe database.


Purge command <definition>
Purge command

Permanently removes previously deleted files and projects from the Visual SourceSafe database.  Once purged, the items cannot be recovered.


read-only file <definition>
read-only file

A file marked as read-only in its file attributes.  Such a file can be viewed in an appropriate text editor, but cannot be modified.  Visual SourceSafe marks the file as read-only when you use the Check In and Get Latest Version commands.


recursive operation <definition>
recursive operation

An operation that is applied both to a parent project and to all the subprojects of that parent.  For example, you can use the Check Out command recursively to check out all the files in the project list simultaneously, and avoid selecting each file individually.


Results Pane <definition>
Results pane

A portion of the Visual SourceSafe Explorer window where results from Visual SourceSafe operations are shown. For example, when you check in a file, this pane shows the file name being checked in.


reverse delta <definition>
reverse delta

The change-storage technology Visual SourceSafe uses, in which incremental changes to a baseline file are stored, rather than each successive version of the file in its entirety.  In Visual SourceSafe, the current version of a file is used as the baseline, and the changes from the previous versions are saved.  This technology results in reduced disk storage requirements and faster access times, because only the current version is always stored in the database in its entirety.


rights propagation <definition>
rights propagation

The default assignment of user-access rights in subprojects based on rights assigned in the parent project.  This default assignment can be changed.


root project <definition>
root project

The highest-level project, with the name $/ in the project list.  All projects in a Visual SourceSafe database are subprojects of the root project.


security <definition>
security

Visual SourceSafe has two levels of security: default security and project security.  Default security provides two types of access rights: Read-Write and Read-Only.  When project security is enabled, four access rights are available per user, per project: Read, Check Out, Add, and Destroy.  Each succeeding right includes all rights preceding it.  The Destroy access right provides unlimited access and is equivalent to Read-Write rights under default security.


shadow folder <definition>
shadow folder

A central, optional folder that contains current versions of all the files in a project.  The shadow folder does not contain the master copy of a file or the local copy of a file.  Instead, it provides a central location from which to view the overall structure of the project and serves as a convenient place to build or compile the project.


shadow variable <definition>
shadow variable

An initialization file variable used to specify the location of a shadow folder.


shared file <definition>
shared file

A file simultaneously used by, and part of, more than one project.


share link <definition>
share link

The link between a file and the one or more projects it may be shared with.  This link serves to update the shared file with any checked-in changes, regardless of which project the file was checked out from.


source code control <definition>
source code control

The management of a file's change history and the file's relation to a larger grouping of related files known as a project.  Source code control is a vital part of the efficient development of software applications.  Visual SourceSafe is a project-oriented type of source code control.


subproject <definition>
subproject

A project within a parent project.


Visual SourceSafe administrator <definition>
Visual SourceSafe administrator

The person responsible for the Visual SourceSafe database.  The administrator uses Visual SourceSafe Administrator to control the location of the database, the user list, and access rights of each user, and performs setup and backup duties on the database.  The administrator's user name is always Admin.


Visual SourceSafe database <definition>
Visual SourceSafe database

The central database where all master copies, history, project structures, and user information is stored.  A project is always contained within one database; multiple projects can be stored in one database, and multiple Visual SourceSafe databases can exist to store multiple projects.


Visual SourceSafe Explorer <definition>
Visual SourceSafe Explorer

The main user interface of Visual SourceSafe, by default comprising two panes [image] the left project pane and the right file pane, as well as the toolbar, status bar, and menus, etc.  Visual SourceSafe Explorer is displayed when you click the Visual SourceSafe icon.


status bar <definition>
status bar

A bar at the bottom of the Visual SourceSafe Explorer window used for displaying project and file status information and current command information.


username <definition>
username

A unique identifying string for a given user.  Used for logging on.


version control <definition>
version control

The control of users' changes to a file, as well as the maintenance of version history on the file.


version number <definition>
version number

A number that indicates the number of revisions a file has undergone since it was added to Visual SourceSafe.  This number is displayed in the History dialog box to help identify specific versions of a file or project.  Version numbers are always whole numbers.


version tracking <definition>
version tracking

The record keeping process of tracking a file's history from the initial version to the current version.  Changes to a file are tracked as part of this process.


wildcard characters <definition>
wildcard characters

The asterisk (*) and question mark (?) are wildcard characters.  You can use these characters  to match patterns.  You can also use wildcard characters and matching characters to further refine a search.

Symbol	Example	Usage
*	wh* finds what, white, and why; *at finds cat, bat, and what	Like the MS-DOS asterisk (*) wildcard character, this asterisk matches any number of characters.
?	b?ll finds ball, bell, and bill	Like the MS-DOS (?) wildcard character, this symbol matches any single character.
A backslash preceding an asterisk or question mark indicates a literal asterisk or question mark: \* or \?  (This is necessary if you want to search for actual asterisks, question marks, or backslashes.)  A double backslash (\\) indicates a backslash.  Any other use of a backslash is ignored.


working folder <definition>
working folder

A specified folder on a user's local computer used to store files when they are checked out of the Visual SourceSafe database.  A user makes changes to files in the working folder, and then checks the modified files back into the Visual SourceSafe database for version tracking.


web site project

A project marked as a web site project in the Visual SourceSafe Administrator.  Such a designation allows special web site commands, such as Deploy, to be used in this project.


visual merge

A merge operation where conflicts are resolved visually, in an easy-to-use graphical interface.


Visual SourceSafe Explorer or one of its components could not be found.

This error has the following cause and solution:

•	The Visual SourceSafe folder is not where expected (in the same folder as SSVB.DLL), or may not be on your path.

Verify that the Visual SourceSafe folder is on your path.  If the problem persists, rerun Visual SourceSafe SETUP.EXE and choose the Client option.


File <file> (file <filename> in Visual SourceSafe) was not found.
File <filename> (file <filename> in Visual SourceSafe) was not found.

This error has the following cause and solution:

•	You attempted to perform a command on a file that is not in Visual SourceSafe, but may be on your local drive.

Verify that the file exists in your Visual SourceSafe project.  If the file does not exist, you can add it to Visual SourceSafe and retry your operation.


File <file> maps to a name over the maximum Visual SourceSafe filename size of <size>.
File <filename> maps to a name over the maximum Visual SourceSafe filename size of <size>.

Visual SourceSafe must map your local filename to a Visual SourceSafe project path.  This error has the following cause and solution:

•	The local filename is valid, but when mapped, it exceeds the maximum size for a Visual SourceSafe project path.

You can either shorten the name of the file, or rename the Visual SourceSafe parent project to a shorter name.


Project <project> was not found.  Would you like to browse for the project?

Visual SourceSafe tried to open a project that could not be found in your  Visual SourceSafe database.  This error has the following cause and solution:

•	You moved or renamed the Visual SourceSafe project in Visual SourceSafe Explorer, then opened your Visual Basic or Visual C++ project that refers to the old Visual SourceSafe project name.

Click Yes to browse for the project if you know the name of the new project.

Click No if you don't want the project to be under source code control.  If you click No, you must manually re-add the project to Visual SourceSafe in order to use source code control features in the future.


File <filename> could not be mapped to the Visual SourceSafe project <project>.  Copy the file to <folder>?

Visual SourceSafe must map the local copy into a Visual SourceSafe project path for this operation to work.  This error has the following cause and solution:

•	You added a file from a folder other than your project folder (or one of its subdirectories) and SourceSafe can't determine which SourceSafe project corresponds to your new file's home folder.

Click Yes if you want to copy the file to the folder named.

Copy the file to a subfolder at or below your project.  If the file is already in Visual SourceSafe in a different project, share the file to your current project and try the operation again.

Click No if you do not want to continue this operation.  You can later copy or share the file and try the request again.


File <filename> could not be mapped to the Visual SourceSafe project <project>.

This error has the following cause and solution:

•	You added a file from a folder other than your project folder (or one of its subdirectories) and SourceSafe can't determine which project corresponds to your new file's home folder.

Visual SourceSafe must map the local copy into a Visual SourceSafe project path for this operation to work.  Copy the file to a subfolder at or below your IDE project.  If the file is already in Visual SourceSafe in a different project, share the file to your current project and try the operation again.

You will continue to get this message for the file as long as the name cannot be mapped.  If this happens, you should remove the file from your project file, copy or share it, and then re-add the file.


Unable to load the source code control provider.

This error has the following causes and solutions:

•	The registry strings used to find the source code control provider dynamic-link library [image] for example, SSSCC.DLL [image] aren’t correct, or you have the wrong version of Visual Basic, or the file SSSCC.DLL is missing.

•	You moved the source code control folder after setup without updating the registry.

•	The setup program failed.

Check your source code provider's setup instructions.

Rerun the Visual SourceSafe setup program.


The source code control provider did not initialize properly.

This error has the following solution:

•	Your system is low on memory or system resources.

Close some applications and try again.

If that doesn't help, reinstall the source code control provider.


The source code control add-in did not disconnect from Visual Basic.

This error has the following solution:

•	Close Visual Basic and re-open it; this is most likely a temporary internal error.


The source code control provider was unable to connect to Visual Basic.

This error has the following causes and solutions:

•	An internal error occurred with OLE and Visual Basic.

•	You are using an incorrect version of Visual Basic.

Reinstall Visual Basic and the source code control provider.


The source code control provider was not able to successfully install menus.

This error has the following cause and solution:

•	There was an internal OLE error.

Reinstall Visual Basic first, the source code control provider next (if necessary), and then OLE (if necessary).


The source code control provider was not able to connect.

A Visual Basic OLE Automation method failed.  This error has the following cause and solution:

•	There was an internal OLE, Visual Basic, or source code control provider error.

Reinstall the source code control provider.


Out of memory; could not complete operation.

You do not have sufficient computer memory to perform the desired operation.  This error has the following causes and solutions:

•	You have too many applications, documents, or source files open.

Close any unnecessary applications, documents, or source files that are open.

•	You are running Microsoft Windows in standard mode.

Restart Microsoft Windows in enhanced mode.

•	You are running Microsoft Windows in enhanced mode, but have run out of virtual memory.

Increase virtual memory by freeing some disk space, or ensure that some space is available.

•	You have terminate-and-stay-resident programs running.

Eliminate terminate-and-stay-resident programs.

•	You have many device drivers loaded.

Eliminate unnecessary device drivers.


The file could not be automatically renamed inside the source code control provider.

This error has the following solution:

•	Open the source code control provider application and manually rename the file.


Unable to automatically remove the file from the source code control provider.

This error has the following solution:

•	Open the source code control provider application and manually remove the file.


Could not connect the source code control project to the current Visual Basic project.

This error has the following cause and solution:

•	The source code control provider could not associate the current Visual Basic project with a source code control provider project.

Run Visual SourceSafe and get the project (if it is already in Visual SourceSafe).

Try to perform the same operation on another project.  If this works, rename the original project and perform the operation again.  If this doesn't work, call Microsoft Technical Support Services.


Unable to add the new project to source code control.

This error has the following cause and solution:

•	There are insufficient source code control provider access rights.

Ask your source code control administrator to increase your access rights, and try again, or try to add the project to a different place in the project tree.

Log on again to Visual SourceSafe with the proper password.

(If you have had other errors just proceeding this one, review their causes for more possible causes.)


The previously loaded project could not be properly closed.

This error has the following cause and solution:

•	While attempting to open a new project, the source code control provider could not properly close the last one.

Exit and restart Visual Basic.


 Unable to set up the source code control menus correctly for this project.

This error has the following cause and solution:

•	There was an internal error during set up of the source code control menu system.

Exit and restart Visual Basic, or exit and restart Windows.


This operation is not supported by the source code control provider.

Some source code providers don’t support all possible source code control commands.  This error has the following cause and solution:

•	You attempted to launch an unsupported operation.

Exit and restart Windows, and report this error to Microsoft Technical Support.


Add Files command failed: The files were not added to source code control.

This error has the following solution:

•	Open the source code control provider application and manually add the files to the project.


 Get command failed: The files were not downloaded from source code control.

This error has the following solution:

•	Open the source code control provider application and manually get the files.

Check the Results window for other error conditions.  If found, correct them and retry this operation.


Check In command failed: The files were not checked in.

This error has the following solution:

•	Open the source code control provider application and manually check in the files.

Check the Results window for other error conditions.  If found, correct them and retry this operation.


Check Out command failed: The files were not checked out.

This error has the following solution:

•	Open the source code control provider application and manually check out the files.

Check the Results window for other error conditions. If found, correct them and retry this operation.


Undo Check Out command failed.  Check files to verify their version status.

This error has the following solution:

•	Open the source code control provider application and manually undo the check out of the files.

Check the Results window for other error conditions.  If found, correct them and retry this operation.


Source code control could not refresh some files.

This error has the following cause and solution:

•	An error occurred during a Get Latest Version command.

Check for free disk space, or restart Windows.

Check the Results window for other error conditions.  If found, correct them and retry this operation.


Some files could not be checked in.

This error has the following cause and solution:

•	An error occurred during a Check In command.

Check for free disk space, or restart Windows.

Check the Results window for other error conditions.  If found, correct them and retry this operation.


Some files could not be checked out.

This error has the following cause and solution:

•	An error occurred during a Check Out command.

Check for free disk space, or restart Windows.

Check the Results window for other error conditions.  If found, correct them and retry this operation.


Some files could not have their check out status undone.

This error has the following cause and solution:

•	An error occurred during an Undo Check Out command.

Check for free disk space, or restart Windows.

Check the Results window for other error conditions.  If found, correct them and retry this operation.


The visual difference operation failed.

This error has the following solution:

•	Open the source code control provider application and manually use the differences command.


The Open Project command from the source code control provider failed.

This error has the following solution:

•	Open the source code control provider application, and then manually get the project.  Then, open the project in Visual Basic.


Unable to start the source code control provider.

This error has the following cause and solution:

•	Visual Basic is not able to start a component of the source code control provider.

Run the source code control provider from the icon, Windows 95 Explorer, or File Manager.


Unable to obtain history for this item.

This error has the following cause and solution:

•	Visual Basic was not able to get the history for this file or project from the source code control provider.

Run the source code control provider and get the history from there.


Unable to determine the properties of this item.

This error has the following cause and solution:

•	Visual Basic was not able to find the properties of this item.

Run the source code control provider and get the properties from there.


Unable to successfully share a file from the source code control provider.

This error has the following solution:

•	Run the source code control provider and share files from there.


Not all requested files could be added into the version control project.
Not all requested files could be added into the source code control project.

This error has the following cause:

•	While adding files to the source code control provider, not all files could be properly replaced.

Check the Results window for other error conditions.  If found, correct them and retry this operation.


You must check out the project file before you can perform this command.

This error has the following cause and solution:

•	You attempted to perform a command that requires check out of the Visual Basic project file before you can check out the project file.

Check out the Visual Basic project file before proceeding, and then try the command again.


This operation requires the Visual Basic project file to be checked out first.

Many operations, such as adding a new file, removing a file, renaming a file, and so forth, require that the Visual Basic project file be checked out first.

•	You performed an operation without first checking out the Visual Basic project file.

Check out the Visual Basic project file before proceeding, and then try the command again.


Your project has not been saved.

This error has the following cause and solution:

•	You have to save your project before using it with source code control.

Save the project, then try your command again.


Not all options could be set correctly.

This error has the following solution:

•	In most cases, options cannot be set correctly due to low memory or disk space.  Free some memory or disk space and try again.


Would you like to get the latest checked-in copy of the files in this project?

Click Yes to get the latest version of the file(s).

Click No to keep the file versions you already have.


Add this project to source code control?

In most cases, click Yes to keep the Visual Basic and source code control projects synchronized.  You may want to click No if you are experimenting with a file that you may add at a later date, or a file that you do not want to add.

Click Yes to add the file to source code control.

Click No to add the file to your Visual Basic project without adding it to the source code control project.


The file has been removed from the Visual Basic project.  Would you also like to remove the file from source code control?

Click Yes to remove the file from the source code control project.  (Deleted files can be recovered later if necessary.)

Click No to remove the file from your Visual Basic project, but keep it in the source code control project.


Would you like to check in all changed files now?

Click Yes to check in all files.

Click No to defer check in until a later time.


All available files have been added to the source code control project.

All files in the Visual Basic project have already been added to the source code control provider.


No files are available to get in this project.

This error has the following cause and solution:

•	There are no files in the current Visual SourceSafe project.

Use the Add Files command to add files.


You do not have any files to check in.

This error has the following cause and solution:

•	You attempted to check in files, but there are none checked out.

If you have made changes to a file that you want to check in, run Visual SourceSafe Explorer, select the file, and on the SourceSafe menu, click Check Out.  Be sure to click the Don't Get Local Copy option in the Check Out dialog box so you don't lose your changes.


All available files have already been checked out.

You attempted to check out a file, but all files are already checked out.


The Results window is full; early entries will be removed from the Results window.

When performing an operation on multiple files, the Results window may quickly fill with status messages.  This warning message has the following cause:

•	The Results window is full.  You won't be able to view some of the earliest entries.


Some old results have been removed to make space for newer results.

This message notifies you that old results have been removed; no action is required.


Because you have not logged on to <provider>, source code control features are not enabled for this project.

This error has the following cause and solution:

•	You canceled your logon to the source code control provider; the source code provider features are not available.

Open a different project, then return to this project and log on.


Would you like to save your files before proceeding with this <provider> operation?

This error has the following cause and solution:

•	You did not save files before performing a source code control provider operation.

Click Yes to save your files.

Click No to allow Visual SourceSafe to overwrite changes made since the last save operation.


The project <project> no longer exists in <provider>.
The project <project> no longer exists under <provider>.

This error has the following cause and solution:

•	The specified project has been deleted (or moved).  You must recover (or select) the specified project before any source code control commands can be applied to it.

If the project was moved, you receive a dialog box to help you search for the new project.  If the project was deleted, you must run the source code control provider to reinstate the project.


The file <filename> could not be added to the Visual Basic project.

This error has the following cause and solution:

•	The file could not be added to Visual Basic.

Try another filename.


File <file> is already checked out.

This error has the following cause and solution:

•	.FRM files can be checked out to only one user at a time.

If necessary, run your source code control provider to find out who the file is checked out to.


The file <file> could not be mapped to the source code control provider project <project>.
The file <filename> could not be mapped to the source code control provider project <project>.

This error has the following cause and solution:

•	The source code control provider does not know which source code control provider project to place the file into, or get the file from.

The source code control provider determines this based on which folder the file is in.  Though the source code control provider can map projects to directories within a project/folder subfolder, files in subdirectories or on other drives create problems, unless there already is an association between the folder that the file is coming from and a source code control provider project.

Add the specified file to a folder at the same level as, or under, the specified project.  If the file is already in the source code control provider, share the file to the current project.


Project <project> was not found.

This error has the following cause and solution:

•	A project was renamed, moved, or deleted.

Click Browse if you want to look through the source code control provider database for the project.


Can't add .FRX file to source code control.

This error has the following cause and solution:

•	An .FRX file was automatically generated to hold resources for the .FRM file, but the .FRX file could not be added to source code control.

Add the file manually.


Can't re-load file <file> in the Visual Basic project.
Can't reload file <file> in the Visual Basic project.

This error has the following cause and solution:

•	The file cannot be re-loaded in the Visual Basic project.

Be sure the Visual Basic project file is checked out. Check the filename, and if it is correct, you may have to reload the file in the Visual Basic project.  This may require getting a new copy of the file from your source code control provider and placing it into your working folder, or may require restarting Visual Basic.


Only one copy of the source code control provider can run at a time.

This error has the following cause:

•	Although multiple, simultaneous sessions of Visual Basic can be run, only one source code control provider can run at a time; this session of Visual Basic has source code control disabled.


File <file> could not be mapped to the Visual SourceSafe project <project>.

This error has the following cause and solution:

•	You must have the file in Visual SourceSafe before continuing the operation.

Click Yes to copy the file to the specified project and continue.

Click No to cancel the operation.


File <file> could not be mapped to the Visual SourceSafe project <project>.

This error has the following cause:

•	The code development environment prohibits copying files directly into Visual SourceSafe.


Your project file has not been saved.  Save your project file before using source code control operations.

This error has the following cause and solution:

•	Source code control requires that you save your project file so that it has a true file to work with.


Your project has not been saved.  Save your project before adding it to source code control.

This error has the following cause and solution:

•	Source code control requires that you save your project so that no project changes are lost.


No corresponding Visual Basic project file for this SourceSafe project.

This error has the following cause and solution:

•	The source code control provider could not locate the Visual Basic project file (.VBP or .MAK file). A project file is required because it stores the list of files included in the project, and the source code control provider uses this list to keep track of file status.


This project is not under source code control.

This error has the following cause and solution:

•	Visual SourceSafe has determined that the current project is not stored in the Visual SourceSafe database.

If you want to add this project to source code control now, save your project and on the Add-Ins source code control provider menu, click Add Project.


Would you like to add file <file> to the current source code control project?

In most cases, click Yes to keep the Visual Basic and source code control projects synchronized.  You may want to click No if you are experimenting with a file that you may add at a later date, or a file that you do not want to add.

Click Yes to add the file to source code control.

Click No to add the file to your Visual Basic project without adding it to the source code control project.


The source code control project already has a makefile named the same as the one you are adding.  Is this the same file?
The source code control project already has a makefile with the same name as the one you are adding.  Is this the same file?

This message has the following cause and solution:

•	You are attempting to add a makefile with the same name as a file already in the source code control provider project.

Check the filename, and rename if necessary.

Click Yes to add the currently selected file, overwriting the old one with the same name.

Click No to cancel the operation.


That source code control project didn't contain the loaded Visual Basic project file.  Try again?

This error has the following cause and solution:

•	You selected a source code control project that didn't contain the proper Visual Basic project file.

Click Yes to resume browsing through the source code control database for the correct project.

Click No to cancel the operation.


The change you just made has changed the Visual Basic project file, but you have not checked the Visual Basic project out yet.

This error has the following cause and solution:

•	You made a change to your Visual Basic project file, but you did not check out the file from the source code control provider first.

Click Yes to check out the project file so you can save your changes.

Click No to keep the project file checked in.  You will not be able to save your changes in the source code control provider.


The file <file> is not a normal file type for adding to a Visual Basic project.

This error has the following cause and solution:

•	The file you are adding to the source code control provider is of a type not generally recognized by Visual Basic.

Click Yes to continue adding it to the source code control provider.

Click No to cancel the add operation.


The file <file> already exists in the source code control project, but your local copy is different.

You (or another user) has added this project to the source code control provider. However, when you tried to add files to the project, a different file with the same name was already in the project. You should use the source code control provider's difference command to see what the differences are, and then check in the proper version.

Rather than using the Add Project command, you could also get the entire project to your local drive, then check out the files you need. Using this method, you would get back in synchronization with the project, but would lose any local changes you had made to the project files.


The file rename operation has been stopped, not all files were saved.

This error has the following cause and solution:

•	You choose not to allow your source code control provider to check out the project file you are renaming.

If you choose not to allow the source code control provider to check out the project file while renaming a file, the operation cannot proceed so that the file does not get renamed in the source code control provider.


You have created a new project.

This error has the following cause and solution:

•	You choose to save your project to a different folder, but your source code control provider can't map the new folder name directly.

The old project is still under source code control, but the new one is not. Use the Add Project command to manually add the new project name to source code control.


The project cannot be added to source code control because the path is too long.

This error has the following cause and solution:

•	The path name for this project is too long.

Use a shorter path name and try again.


SRCSAFE.INI file not found in folder <folder>.

This error has the following cause and solution:

•	You have chosen a folder path in the Connect to Visual SourceSafe dialog that does not contain a SRCSAFE.INI file.

You need to choose the folder where their database information exists.  This is typically on the server where SourceSafe is installed.


<string> contains an invalid character.

This error has the following cause and solution:

•	You have entered a data path value in the Connect to  Visual SourceSafe dialog that contains an invalid character.

Data path names should not contain the ( )[ ] or blank characters.


Project <project> has been removed and must be recovered before opening.

This error has the following cause and solution:

•	You have deleted a project and then tried to open it from Visual Basic or Visual C++.

You cannot open a deleted project until it is recovered.


File <file> has not been changed.

This error has the following cause and solution:

•	You are attempting to check in a checked out file that you have not changed.

Click Yes, and Visual SourceSafe checks it in anyway.  (Clicking Yes All checks in all selected files.)  A check in creates a new version of the file, with an optional comment.

Click No, and Visual SourceSafe undoes the check out of the file.  (Clicking No All undoes the checkout for all selected files.)  No new version of the file is created in this case.


Internal error: please exit and restart Visual Basic.

This error has the following cause and solution:

•	An internal error has occurred in Visual Basic or Visual SourceSafe.

Save your work, exit from Visual Basic and Visual SourceSafe, and restart those programs if you still need to use them.


Some files have not been named yet.

This error has the following cause and solution:

•	You have not named all your files.

Name your files using the Visual Basic Save File command before proceeding with your operation.


The file '<file>' is not under source code control.

This error has the following cause and solution:

•	You have selected a file that is not under source code control.

Use the Add Files command to add the file to your source code control provider before trying to check it out or use source code control provider functions on it.


The file '<file>' is no longer connected to this source code control project.

This error has the following cause and solution:

•	You have selected a file that is no longer under source code control in this project.

The file has possibly been deleted from the source code control provider, or moved to a different project. Use the Add Files command to add the file to your source code control provider in the proper project, or search the source code control database for the file if it may be part of another.


Please save and check-in your makefile.
Please save and check-in your Visual Basic project file.

This error has the following cause and solution:

•	You have made changes that modify your Visual Basic project file.

You need to save and check-in your makefile.  Otherwise, your project will contain references to the copied-in files in their old locations instead of the current locations.


Errors during load of file <file>.

This error has the following cause and solution:

•	Errors were encountered while loading the file.

The file may or may not have been loaded successfully by Visual Basic.  Try opening the file again, or check the file for corruption.


You have not added the makefile to source code control.
You have not added the makefile to source code control. This project has not been connected to source code control.

This error has the following cause and solution:

•	You added a new project to source control, but did not include the makefile.

Re-add the project and include the makefile.


A VB project by this name already exists in the source code control project <project>.
A VB project by this name already exists in the source code control project <project>.  Would you like to reconnect this VB project to the existing source code control project?

This error has the following cause and solution:

•	You tried to add a project, but a project with that name was already under source control.

Choose Yes to reconnect to the existing project, or choose No if the project in source control is a different project by the same name.  Then, choose a new name for the new project.


Would you like to check out file '<file>'?

This error has the following cause and solution:

•	You tried to edit the Visual Basic file <file>, without having it checked out.

Choose Yes to check out the file, or No to cancel the operation.


You can share another makefile into this source code control project, but the makefile has not been added to the VB project.

This error has the following cause and solution:

•	You tried to share a makefile from another project into the current project, but have not added the makefile into SourceSafe.

Add the makefile into the proper project first.


The Get operation failed.

This message has the following cause and solution:

•	You have unsaved objects that would be lost if the operation proceeded.

Save all objects in your project to a file, and then try again.


The Check In operation failed.

This message has the following cause and solution:

•	You have unsaved objects that would be lost if the operation proceeded.

Save all objects in your project to a file, and then try again.


The Get operation failed.
The Undo Check Out operation failed.

This message has the following cause and solution:

•	You have unsaved objects that would be lost if the operation proceeded.

Save all objects in your project to a file, and then try again.


The Check Out operation failed.

This message has the following cause and solution:

•	You have unsaved objects that would be lost if the operation proceeded.

Save all objects in your project to a file, and then try again.


The Share operation failed.

This message has the following cause and solution:

•	You have tried to share a file that has the same name property as one in the target project.

There are several possible causes for this message.  One is if you have not assigned the name property in one of your files, you could be conflicting with a file in the target project (where the name property also was not assigned or is identical). In this case, assign the name property of the file in your current project, and then try again.

Other possibilities are that the project file is checked out to someone else, or you were not able to check out the project file. Check the file checkout status to determine if this is the case.  Or, there could have been a Visual SourceSafe internal error.


You have tried to change the Visual Basic project file without checking it out first.

This message has the following cause and solution:

•	You need to check out the Visual Basic project file before you can make changes to it.

You must check out the project file and then make your changes.


This operation requires the Visual Basic project file to be checked out first.
This operation requires the Visual Basic project file to be checked out first.  Would you like to check out the Visual Basic project file?

This message has the following cause and solution:

•	You need to check out the Visual Basic project file before you can make changes to it.

You must check out the project file and then make your changes.


The source code control add in could not connect to Visual Basic.
Unable to initialize the host application for source code control.

This message has the following cause and solution:

•	SourceSafe could not connect properly to your development host.

Rerun the setup program for your development environment, and then rerun the Visual SourceSafe setup program.


Unable to connect Visual Basic to source control.
Unable to connect Visual Basic to source control.  Please check the installation of the source code control add-in.

This message has the following cause and solution:

•	SourceSafe could not connect properly to your development host.

Rerun the setup program for Visual SourceSafe.


There is no makefile associated with this project, unable to create a Visual Basic project from this <project> project.

This message has the following cause and solution:

•	You tried to create a Visual Basic project from source control, but specified an invalid project.

Check the project name, and try again.


Another user (<user>) has placed this database under source code control and is the only person who should work with it.

This message has the following cause and solution:

•	You are trying to open a database owned by another user.

You were not the last user to use this file. If you continue, you will overwrite their changes and checkout status.  Log out from Visual SourceSafe, and then get your own copy of the file using the Create <object> From SourceSafe command.


Could not create a valid file name for <file>.

This message has the following cause and solution:

•	You can only add modules to Visual SourceSafe if the module name is a valid filename. The file name you chose is not valid.

Rename your object to something with a valid filename.

If you mistyped the file name, please try again with a valid file name. If you believe the file name is valid, and are working in a mixed-operating system environment, the problem may be that the file name you chose does not translate properly in one of the other operating system environments connected to your Visual SourceSafe database.  In this case, try another filename.


You have not added the .ACB file to source code control to have a complete database.

This message has the following cause and solution:

•	You added an Access project, but chose not to add a .ACB file.

Re-add the project to source control, and include the .ACB file.


A database by this name already exists in the source code control project <project>.
A database by this name already exists in the source code control project <project>.  Would you like to reconnect to it?

This message has the following cause and solution:

•	You tried to add a project, but a project with that name was already under source control.

Choose Yes to reconnect to the existing project, or choose No if the project in source control is a different project by the same name.  Then, choose a new name for the new project.


The Get operation failed.
The History operation failed.

This message has the following cause and solution:

•	You have unsaved objects that would be lost if the operation proceeded.

Save all objects in your project to a file, and then try again.


Required supporting files could not be added to source code control, the Check In operation failed.

This message has the following cause and solution:

•	You tried an Add operation, but it failed when SourceSafe tried to add supporting project files (for example, the .frx form file).

Add each file separately to source control.


The item was not removed from the <provider> project.

This message has the following cause and solution:

•	This is usually caused by an internal SourceSafe error.

Remove each file separately from source control.


The item was not renamed in the <provider> project.

This message has the following cause and solution:

•	This is usually caused by an internal SourceSafe error.

Rename each file separately in source control.


The file could not be reloaded into the host IDE.

This message has the following cause and solution:

•	This is usually caused by an internal application error.

Close the project and re-open it.


You have created a new project with a different name.
You have created a new project with a different name.  The new project is no longer associated with source code control.

This message has the following cause and solution:

•	You have renamed a project and the renamed project is no longer in source control.

Add the new project to source control, if desired.


The file that was renamed had a tagalong file which could not be automatically renamed in source control.

This message has the following cause and solution:

•	This is usually caused by an internal SourceSafe error.

Manually rename the tagalong file.


You have chosen not to check out the Visual Basic project file, all the changes you have made to the project during this session will be lost.

This message has the following cause and solution:

•	This is a warning that if you do not check out the project file, any changes you make in this editing session will not be saved in source control.

Check out the project file if you want to save your changes.


The copy of the Visual Basic project file in the version control database has changed, you can no longer save your current changes.
The copy of the Visual Basic project file in the version control database has changed, you can no longer save your current changes.  You must check-out the project file and remake your changes.

This message has the following cause and solution:

•	This is a warning that another user changed the project file while you were working.

Check out the new version of the project file and redo your changes.


Failed to initialize the current project.
Failed to initialize the current project.  Please exit and reload this project.

This message has the following cause and solution:

•	This is usually caused by an internal SourceSafe error.

Exit and reload the project. If that doesn't solve the problem, exit and reload your development environment application.  If the problem persists, reboot your computer.


Out of Memory - could not complete operation.

This message has the following cause and solution:

•	Your computer has run out of memory.

Close unused applications.  If the problem persists, restart your computer.


Only a single project can be under source control at a time with this source code control provider.

This message has the following cause and solution:

•	Some source control providers can handle only one project at a time.

Contact your vendor for an updated version of the source code control provider.  Or, choose a more advanced source control provider, or don't use multiple projects..


Unable to initialize the host application for source code control.

This message has the following cause and solution:

•	The source provider could not connect properly to the host development environment..

Rerun the setup programs for your host development environment and source control provider..


Failed to initialize the source code control provider.

This message has the following cause and solution:

•	The source provider could not connect properly to the host development environment..

Rerun the setup programs for your source control provider..


Failed to reload the project.

This message has the following cause and solution:

•	An internal application error occurred.

Close this project from the file menu and re-open it to get the correct version of all files loaded into memory.


Failed to add files to <project>.

This message has the following cause and solution:

•	Visual SourceSafe couldn't save the files that you want to add, and they contain unsaved changes.

The Visual SourceSafe operation may have failed, you may not have add rights in this project, or you could have run out of memory.  Save your files manually and try again.  If that fails, check your Visual SourceSafe connection and try again.


You do not have any files checked out from source code control.

This message has the following cause and solution:

•	You chose the Add, Checkout, Get, Check In, Undo Check Out command, but after careful checking, no files were available for the operation.

This error sometimes occurs if someone deletes the file that you wanted to operate on (or deletes the whole project, for that matter)- make sure your project is still there.  Next, make sure you have something checked out.


Would you like to add the new file(s) to the current source code control project?

This message has the following cause and solution:

•	You are adding, either directly or indirectly through a wizard or other tool, several files to source control.

Choose Yes to add the file(s), or No to cancel the operation.


The share operation succeeded, but the files could not be added to the current project.

This message has the following cause and solution:

•	The share operation succeeded, but trying to add the file to the project failed.

Check that the name property of the file does not conflict with the name property of an existing form, module, class module, or other Visual Basic file.


The filename '<file>' contains illegal characters.  The file will be ignored.

This message has the following cause and solution:

•	You put one or more illegal characters (like a semicolon, slash, backslash, colon, etc) in the specified filename.

Rename your file using legal characters.


This project was named '<name>' but has been moved, copied, or renamed.

This message has the following cause and solution:

•	Once you place an Access database under source code control, you are not allowed to rename it or move it to a different directory, or to work with copies of it.  When you open a database under source code control which has been moved, renamed, or copied, this message will be displayed and all source code control functions will be disabled for this database.

Do not work with a copy of an Access database which is under source code control.  Use the Create Database from SCC command to make a new database in the desired location.

If the database has been moved, return it to its original location and reopen it.  Source code control functions will return to normal.  Likewise, if it has been renamed, restore its original name.


Could not create a working folder for this project.

This message has the following cause and solution:

•	The working folder you specified could not be created.

You may not have permission to create a folder on the computer you specified, or the drive may be full, or the name you choose may already be in use.  Try specifying another name.


The file <file> already exists in the source code control project, but your local copy is different.

This message has the following cause and solution:

•	You tried to add a file to your project when a file by that name already existed in the project.  The file was not added, and your local copy has not been changed.

Choose a different name for the file you want to add.


You have not added enough files to source code control to have a complete project.

This message has the following cause and solution:

•	You tried to add some files to source control, but they are not enough to completely define a project. This project has not been connected to source code control.

Visual SourceSafe needs to maintain all the files in the project.  Add the complete set to the Visual SourceSafe project.


The <file> may have changed. Undo checkout and lose changes?

This message has the following cause and solution:

•	This confirmation message asks if you want to continue with your Undo Check out command, even though it may mean losing changes you have made to your local file.

Choose Yes to undo your checkout, and No to cancel the operation.


Some file(s) could not be saved.  The project was not added to <provider>.

This message has the following cause and solution:

•	You are adding a project to source control without saving changes.

SourceSafe was not able to save some of your changes.  You may not have write permission on some files, or you may have a network error.


An error occurred while trying to connect to the <project> project.

This message has the following cause and solution:

•	The source control provider could not initialize the source control project.

Exit your development environment  and re-start it.  If this does not clear the error, re-run your source control provider’s setup program.  Check your system resources, especially memory and disk space.


Add this project to <project>?

This message has the following cause and solution:

•	You have not added this project to source control.

Choose Yes to add this project to source control.  Choose No to leave this project out of source control (for instance, to debug code first).


You don't have a source code control program (such as Microsoft Visual SourceSafe) installed on your machine.

This message has the following cause and solution:

•	You have not added source control programs to your computer.

The source code control commands are therefore not available.  Choose Yes to display this warning the next time you try to use source control commands, or No to disable this warning message.

For Visual SourceSafe users, run NETSETUP.EXE from your SourceSafe folder to get source control capabilites. For other source control providers, re-run Setup for your provider.


The new name cannot be used because an object with that name already exists in <provider>.

This message has the following cause and solution:

•	You are attempting to rename a file/object, and the new name is the name of an object/file that already exists in source code control.

Choose a different name for the file/object, or rename/delete the existing object that has the desired name.


# The new name cannot be used because it is not a valid filename.
The new name cannot be used because it is not a valid filename.

This message has the following cause and solution:

•	You are attempting to rename a file/object, and the new name is not a valid filename (typically because it contains invalid characters).

Choose a different name for the file/object.


No files are available to be checked out from source control.

This error has the following cause and solution:

•	There are no unchecked-out files in the current Visual SourceSafe project.

To check out a file not yet added to source control, use the Add Files command to add files.  If the file is already in your project, make sure it is not already checked out.

This error sometimes occurs if someone deletes the file that you wanted to operate on (or deletes the whole project, for that matter)- make sure your project is still there.


All available files have already been added to source control.

This error has the following cause and solution:

•	All the files in your current development project have already been added to source control.

If you want to check in a file that is not yet in your development project, first add the file to your development project.  Visual SourceSafe will prompt you to add it to source control.


Would you like to remove the file '<file> from source code control?

This message has the following cause and solution:

•	You have removed an object from the development project.

Choose Yes to remove the object from source control as well, or No to leave the object in the source control project.


The file <file> is no longer under source code control, the operation failed.

This message has the following cause and solution:

•	Some user deleted a file from your Visual SourceSafe database during your session, and you tried to use a context menu to get it.

Re-add the file to source control, check to find out who deleted it and why, etc.


The <project> project that you selected does not contain this IDE project.

This message has the following cause and solution:

•	This warning informs you that while trying to browse for a deleted project you picked the wrong project.

Re-try the browse operation.


The <project> project that you selected does not contain this VB project.

This message has the following cause and solution:

•	This warning informs you that while trying to browse for a deleted project you picked the wrong project.

Re-try the browse operation.


Would you like to get the latest version of all files in project <project>?

This message has the following cause and solution:

•	This query is asking if you want to get all the latest file versions in your project’s working folder.

Choose Yes to get the latest versions of all files in the project.  Choose No to cancel.  You can use the Options command to turn this query message off.


Since you have not logged into <project>, source code control features are not enabled for this session.
Since you have not logged into <source control provider>, source code control features are not enabled for this session.

This message has the following cause and solution:

•	You did not log on to the source control provider.

Re-open your project, and log on to the source control provider to use source control features.


The project <project> no longer exists under source code control.  You must either recover or re-create the project before you can use this project with source code control.

This message has the following cause and solution:

•	Your project has been deleted (or moved) by another user.

Click OK if you want to try to find the project. If the project has been deleted, choose Cancel.  Once you click Cancel, the database will be detached from source code control, and you can re-add the project to source control (but you will lose any historical information on this project).

If you can find out who deleted or moved your project, you may be able to recover the project and its history (for example, if your source control administrator has archived your project to a backup tape).


Add this project to <project>?

This message has the following cause and solution:

•	You created a new project, or opened a project which hasn't been under source control before.

Choose Yes to add the project, or No to cancel the operation.


Another user (<user>) has placed this project under source code control and is the only person who should work with it.

This message has the following cause and solution:

•	Another user has this database under source control and you opened it.  You will overwrite all of the other user's changes unless you exit immediately.  If the other user had anything checked out, his or her changes will be lost the next time they use the Get Command.

Exit immediately, or sacrifice the other user's changes.


No files are available to get from source code control.

This message has the following cause and solution:

•	You chose the Get command, but after careful checking, no files were available for the operation.

This error sometimes occurs if someone deletes the file that you wanted to operate on (or deletes the whole project, for that matter)- make sure your project is still there.  Next, make sure you have something checked out.


This is an integration only project; checking out files is not allowed from the SourceSafe Explorer.

This message has the following cause and solution:

•	You chose the Check Out command on files restricted from checking out except while in the host development environment.

Open the project from within Visual Basic, Access, or other development environment and check the files out from there.


Unable to check out the file <file> because it is already checked out.

This message has the following cause and solution:

•	The file you chose is already checked out.

Files stored in binary format cannot be checked out by more than one person at once, because Visual SourceSafe could not merge in conflicting changes made by multiple users.


Would you like to check in all files which are checked out to you in project <project>?

This message has the following cause and solution:

•	You are closing the development environment leaving files checked out.

When you close your development environment, Visual SourceSafe reminds you that you have files checked out of the project and prompts you to check them back in.  You do not have to check them back in, but leaving them checked out may prevent other users from checking them out.


Add Files to Source Code Control Command (Development Environment)

See Also

Copies a file, or group of files, from your development environment project into a Visual SourceSafe project.

To use the Add Files to Source Code Control command

•	After you've added a development environment project to source code control, on the Tools SourceSafe menu, click Add Files to Source Code Control.

Remarks

Use the Add To Source Code Control dialog box to place a development environment file into the source code control database.  You can use this command only with files that are already part of your development environment project.  If you have a file you want to add to source code control that isn't part of any project, add it to your development environment project first.

Note   Development environment files already added to the current source code control project are not displayed under Files To Be Added.

Dialog Box Options

Files To Be Added

Files available to be added to the source code control database.  Click the check box next to the file(s) you want to add.

Comment

Type an optional comment for all selected files.

OK

Adds file(s) to source code control.

Cancel

Cancels the Add Files To Source Code Control command.

Select All

Selects all files listed.


Add Files to Source Code Control Command (Development Environment) See Also
See Also

Add Project To Source Code Control Command

Adding Files to the Visual SourceSafe Database (Visual SourceSafe)

Getting Started with Visual SourceSafe (Visual SourceSafe)


Show Differences Command (Development Environment)

See Also

Compares a selected file in your development environment project to the current version stored in the source code control provider database and shows you the differences, if any.

To use the Show Differences command

•	After you've added a project to your source code control provider, on the Tools SourceSafe menu, click Show Differences.

Remarks

Most commonly, you use the Show Differences command immediately before you check in a file to compare your modified copy of the file to the master copy.  This gives you a list of the changes you have made, which can be helpful for generating your comment.

When you use the Show Differences command on an ASCII text file, your source code control provider displays a color-coded list of line differences between the database-stored version of the file and your local copy.

For binary files, your source code control provider tells you if the local copy of the file is different from the master copy, but cannot display the differences.


Show Differences Command (Development Environment) See Also
See Also

File Difference Dialog Box (Visual SourceSafe)

Show Differences (File) Command (Visual SourceSafe)

Show Differences (Project) Command (Visual SourceSafe)


File Difference Dialog Box (Visual SourceSafe)

See Also

By default, Visual SourceSafe uses the Visual display option, with line width calculated to fit on your screen, and no context lines.  If you specify a UNIX display, Visual SourceSafe uses the Ignore Case and Ignore White Space options.  The Visual display shows all lines (infinite context).

Visual

Shows the entire file, with annotations of the changes.

SourceSafe

Shows a list of lines that were added, deleted, and changed, optimized for readability.

Unix

Shows differences information in the format used by the UNIX Diff utility.

Ignore Case

Shows differences without regard for upper- and lowercase differences.

Ignore White Space

Shows differences without regard for spacing characters, such as tabs.

Report

Sends a report to the Clipboard, a text file, or a printer.

Project

Displays the Project Difference dialog box.

Advanced Options

Ignore OS Differences

Tells Visual SourceSafe to ignore operating system line-break character differences.  This is useful if you are comparing files across a network where one computer is a Macintosh, for example, and the other is operating with Microsoft Windows NT.

Show Context Lines

Includes the specified number of context lines in the differences display.  Context lines are the lines in your file surrounding the line identified as different by Visual SourceSafe.  For example, setting Show Context Lines to three means you'll see three context lines above and three context lines below the difference line.

Save Settings

Saves your selected settings for future use.


File Difference Dialog Box (Visual SourceSafe) See Also
See Also

Show Differences (Project) Command (Visual SourceSafe)


Show History Command (Development Environment)

See Also

Shows the history of a file or project under source code control.

To use the Show History command

•	After you've added a development environment project to your source code control provider, on the Tools SourceSafe menu, click Show History.

Remarks

Every time you check in a file or project to your source code control provider, the file or project is given a new version number.  Use the Show History command to display a list of a file's or project's past versions.

Note   By default, the Show History command displays the File History Options dialog box; click Projects to display the Project History options dialog box.

The versions listed start with the most recent and return to the creation of the file or project.  Visual SourceSafe provides information about the version number, which can be used with other commands (such as Get Latest Version) to indicate a specific version.

By default, the history of a project includes the histories of all its files, but is not recursive and does not include subprojects.


Show History Command (Development Environment) See Also
See Also

File History Options Dialog Box (Visual SourceSafe)

History of File Dialog Box (Visual SourceSafe)

History of Project Dialog Box (Visual SourceSafe)


File History Options Dialog Box (Visual SourceSafe)

See Also

Labels Only

Includes only labels in the project or file history.

From

Type a time, date, version, or label.  Use the prefix D to indicate a date or time, and the prefix L to indicate a label.  For example "D02/29/95;12:15" or "LBeta1."

To

Type a time, date, version or label.  Use the prefix D to indicate a date or time, and the prefix L to indicate a label.  For example "D02/29/95;12:15" or "LBeta1."

User

Type a username to show a history of the files worked on by the specified user.

OK

Displays the History of File dialog box.

Cancel

Cancels the Show History command.

Project

Displays the Project History Options dialog box.  The Project History Options dialog box contains the same options as those in the File History Options dialog box, along with two additional options: Include Files includes file information in the History of Project display; Recursive includes subprojects and all files within the subprojects.  Click OK to display the History of Project dialog box.


File History Options Dialog Box (Visual SourceSafe) See Also
See Also

History of File Dialog Box (Visual SourceSafe)

History of Project Dialog Box (Visual SourceSafe)


Share Files Command (Development Environment)

See Also

Makes the selected file a member of the current project, or creates a new branch project.

To use the Share Files command

After you've added a development environment project to your source code control provider, on the Tools SourceSafe menu, click Share Files.

Remarks

Note   To share a file, you create a share linkGloss_sharelink among projectsGloss_project.  The file then exists simultaneously in two (or more) projects.  When you check in the file to any one of the projects, your changes are automatically checked in to all of them.

If you create a branch, changes made in the branched file no longer propagate to the originating project, and vice versa.

When you share a project, you create a new project under the current project that is an exact duplicate of the specified project.  All the files in the new project are shared with the corresponding files in the originating project, and changes to one are reflected in the other during check in.

Note   When sharing a project with Visual Basic form files (.FRM), be sure to share the associated .FRX file created by Visual Basic.  If you don't, the shared project will not have all the files it needs and will not work correctly.


Share Command See Also
See Also

Share Files Dialog Box Options (Visual SourceSafe)

Branching Files and Projects (Visual SourceSafe)

Sharing Files (Visual SourceSafe)

File Types Options Tab (Visual SourceSafe)


Options Command (Development Environment)

See Also

Customizes your source code control provider environment.

To use the Options command

•	After you've added a development environment project to your source code control provider, on the Tools SourceSafe menu click Options.

Remarks

The Options command displays the Source Code Control Options dialog box.

Dialog Box Options

For each option, you can specify Yes, No, or Ask.

•	Get checked in version of project files when opening a project? (No is the default.)

•	Check in files when closing the project?  (Ask is the default.)

•	Add files to source code control when adding them to Visual Basic?  (Yes is the default.)

•	Remove files from source code control when deleting them from Visual Basic?  (Ask is the default.)

Advanced

Displays advanced options.

OK

Confirms selections.

Cancel

Cancels selections.


Options Command (Development Environment) See Also
See Also

Advanced General Options (Visual SourceSafe)

Advanced Local Files Options (Visual SourceSafe)


Create Project from SourceSafe Command (Development Environment)

See Also

Copies a project to your hard disk when the project is in source code control but not on your hard disk.

To use the Open New Project command

•	On the Tools SourceSafe menu, click Download SourceSafe Project.

Note:   After you locate a project you want, this command opens it in your development environmentGloss_developmentenvironment and automatically gets all of its files from the Visual SourceSafe database.


Open New Project Command (Development Environment) See Also
See Also

Open SourceSafe Project Dialog Box (Visual SourceSafe)


Create local project from SourceSafe Dialog Box (Visual SourceSafe)

Creates a new development project from an existing SourceSafe project.

To use the Download SourceSafe Project command

•	On the Tools menu, click the name of your source code control provider, and then click Download SourceSafe Project.

Note   Use the Download SourceSafe Project dialog box to specify an existing SourceSafe project containing a project you need, and then choose a folder on your local computer in which to place the new project files.  Microsoft Access will open the newly created project upon completion.

Dialog Box Options

Create a new project in this folder

The working folder for the selected project.  Click Browse to create or change the working folder.

SourceSafe Project to download

Visual SourceSafe project list.  Click the project you want to open.

OK

Visual SourceSafe gets the files, places them in your working folder, and opens the project in your development environment so that you can edit it.

Cancel

Cancels the Download SourceSafe Project command.


Run Command (Development Environment)

Starts your source code control provider.

To use the Run command

•	On the Tools SourceSafe menu, click Run.  In some cases, you may need to type your username and (if applicable) your password, and then click OK.

Remarks

Note   When you use the Run Visual SourceSafe command, you have access, through Visual SourceSafe Explorer, to all of the Visual SourceSafe features and commands.  The Visual SourceSafe commands available from the Tools SourceSafe menu are a subset of the full Visual SourceSafe command set.


Add Project To Source Code Control Command (Development Environment)

See Also

Adds the current development environment project to the source code control database.

To use the Add Project To Source Code Control command

•	On the Tools SourceSafe menu, click Add Project to Source Code Control.

Note   If you specify the name of your source code control provider, that name is displayed in place of "Source Code Control."

Remarks

The Add Project to Source Code Control command takes the selected files in the development environment project window and creates a new source code control project containing those files.  This command is available only when you select a project not already under source code control.  Each selected file is automatically added at this time.


Add Project To Source Code Control Command (Development Environment) See Also
See Also

Add SourceSafe Project Dialog Box (Visual SourceSafe)


Add SourceSafe Project Dialog Box (Visual SourceSafe)

Project

Type the name of the Visual SourceSafe project you want, or click in the project list to choose a project.  You can enter a full project path specification (as in $/CODE/RESOURCES) or just type a project name to have a project created under the current project.

OK

Adds the current development environment project to Visual SourceSafe.

Cancel

Cancels the Add Project to SourceSafe command.

Create

Creates a new Visual SourceSafe project.  Type a name under Project and click Create.


Get Latest Version Command (Development Environment)

See Also

Gets the selected files from your source code control provider and places a read-only file in the development environment project.

To use the Get Latest Version command

•	On the Visual Basic Tools SourceSafe menu, click Get Latest Version.

Dialog Box Options

Files to Get/Check In

Selects the file or files you want to get or check in.

OK

Confirms your selections.

Cancel

Cancels your selections.

Select All

Selects all files listed.


Get Latest Version Command (Development Environment) See Also
See Also

Get Latest Version Command Advanced Options (Visual SourceSafe)

Getting, Checking In, Checking Out, and Viewing Files

Local Files Options Tab


Get Latest Version Command Advanced Options (Visual SourceSafe)

Sets default Get Latest Version command options.

Replace Writable

Determines Visual SourceSafe's behavior when you attempt to get a file that is already marked as writable in your working folder.  Select one of the following in the list box:

•	Ask [image] Asks you what to do in each case.

•	Replace [image] Visual SourceSafe replaces the file with a read-only version.

•	Skip [image] Skips the Get Latest Version operation.

•	Merge [image] Merges the changes between the checked out-file and the one you are now getting or checking out.

•	Default [image] Uses the default set on the Local Files Options tab in the SourceSafe Options dialog box (Tools menu).

Set File Time

Changes the time assigned to the Get Latest Version operation.  Select one of the following in the list box: current time, the last file modification time, the last file check-in time, or the default time (set on the Local Files Options tab).

End of Line

Specifies the end-of-line character that Visual SourceSafe gives to each line in the file it retrieves.  Select one of the following in the list box: line feed (LF) for the UNIX platform, carriage return (CR) for the Macintosh, carriage-return/line-feed (CR/LF) for MS-DOS/Windows, or the default (set on the Local Files Options tab).

Make Writable

Retrieves the file and makes it writable.  This is not equivalent to a Check Out operation, because the Get Latest Version command is non-exclusive [image] one or more people can perform the Get Latest Version command on the same file.  You cannot check in changes after a Get Latest Version operation with this option set.


Check Out Command (Development Environment)

See Also

Checks out a copy of the selected file(s) from your source code control provider and places a writable copy in the corresponding development environment working folder.

To use the Check Out command

•	On the Visual Basic Tools SourceSafe menu, click Check Out.

Dialog Box Options

Files to be Checked Out

Lists the files available for check out.  Click the files you want to check out, or click Select All to select all files listed.

Comment

Type a brief description of the reason for the check out.

OK

Confirms Check Out.

Cancel

Cancels the Check Out command.

Select All

Selects all files listed.


Check Out Command (Development Environment) See Also
See Also

Check Out Advanced Options (Visual SourceSafe)

Getting, Checking In, Checking Out, and Viewing Files

Check Out Status Properties Tab

Local Files Options Tab


Check Out Advanced Options (Visual SourceSafe)

Sets default Check Out command options.

Replace Writable

Determines how Visual SourceSafe behaves when you try to check out a file that is already marked as writable in your working folder.  Select one of the following in the list box:

•	Ask [image] Asks you what to do with each file.

•	Replace [image] Replaces the file with a read-only version.

•	Skip [image] Skips the check out operation.

•	Merge [image] Merges the changes between the checked out-file and the one you are now getting or checking out.

•	Default [image] Uses the defaults set on the Local Files Options tab in the Options dialog box (Tools menu).

Set File Time

Changes the time assigned to the check out operation.  Select one of the following in the list box: current time, the last file modification time, the last file check-in time, or the default time (set on the Local Files Options tab).

End of Line

Specifies the end-of-line character that Visual SourceSafe gives to each line in the file it retrieves.  Select one of the following in the list box: line feed (LF) for the UNIX platform, carriage return (CR) for the Macintosh, carriage-return/line-feed (CR/LF) for MS-DOS/Windows, or the default (set on the Local Files Options tab).  Visual Basic users should always set this to CR/LF.

Don't Get Local Copy

Tells Visual SourceSafe not to copy the file to your working folder.  Visual SourceSafe records that the file is checked out, but does not give you a new copy.


Undo Check Out Command (Development Environment)

See Also

Overwrites your changes to a file, and copies the latest checked in version to your development environment working folder.

To use the Undo Check Out command

•	On the Visual Basic Tools SourceSafe menu, click Undo Check Out.

Dialog Box Options

Files to Un-Check Out

Lists the currently checked out files.  Click the files whose check out you want to undo, or click Select All to select all the listed files.

OK

Confirms the selection.

Cancel

Cancels the selection.

Select All

Selects all files listed.


Undo Check Out Command (Development Environment) See Also
See Also

Getting, Checking In, Checking Out, and Viewing Files

Local Files Options Tab

Undo Check Out Advanced Options (Visual SourceSafe)


Undo Check Out Advanced Options (Visual SourceSafe)

Local Copy

•	Replace [image] Replaces the file in your working folder [image] it performs the Get Latest Version command on the file.  This keeps your working folder up-to-date with the contents of the project; all your changes are ignored.

•	Delete [image] Deletes the file from your working folder.

•	Leave [image] Leaves the file alone.

•	Default [image] Replaces the file in your working folder, unless you have the Delete Local Files After Add or Check In set on the Local Files Options tab.


Check In Command (Development Environment)

Checks in changes made in your development environment working folder to your source code control database.

To use the Check In command

•	On the Visual Basic Tools SourceSafe menu, click Check In.

Dialog Box Options

Files To Be Checked In

Lists the files available for check in.  Click the files you want to check in, or click Select All to select all the files listed.

Comment

Type an optional comment.

Keep Checked Out

Updates the source code control database with your changes but keeps the file checked out to you.

OK

Checks in the selected files.

Cancel

Cancels the Check In command.


Find MakeFile Dialog Box (Development Environment)

Identifies your development environment project file so the source code control provider can properly perform its operations.  Appears only when you perform operations on projects that contain more than one makefile is in the same folder.

Dialog Box Options

Select the Visual Basic project file

Select the development environment project file for the project you want to work with.

OK

Opens the selected project file.

Cancel

Cancels the command.


Source Code Status Dialog Box (Development Environment)

Displays the status of the current source code control command.

Dialog Box Options

Cancel

Cancels the current source code control operation.


Source Code Control Results Window (Development Environment)

Displays the results of the last source code control command.

Dialog Box Options

Close

Closes the Source Code Control Results window.


Integration Options Tab

Displays information about the integration between your project and the corresponding Visual SourceSafe project.

To display the Integration Options tab

•	On the Tools SourceSafe menu, click SourceSafe Options, and then click the Advanced button. Then, choose the Integration tab.

Access Rights

You must have the Read access right to use this tab.

Remarks

The Integration Options tab is most useful for seeing how your SourceSafe and development projects are connected. However, you can also set a couple options on this tab: whether to display intermediate dialog boxes for the History and Show Differences command, and whether to prompt for the SourceSafe database to use when opening a new project.

Tab Options

SourceSafe project

Shows the full name of the SourceSafe project associated with this development project.

Database name

Displays the name (if any) of the Visual SourceSafe database the project is stored in.

Database path

Displays the path to the SourceSafe database the project is stored in.

Data specifier

Displays the data folder for a specific project. (Your SourceSafe administrator can set up different data folders for different projects using the Data_Path variable.)

Display dialog box for

Check the box corresponding to the command if you want an options dialog box displayed when you select that command.

Choose SourceSafe database

Set to Use Default Database to always look in the default SourceSafe database for your project information. Set to Prompt to display a prompt dialog box, allowing you to specify the database name, path, and data specifier each time you open a project.

OK

Sets the options as specified on the tab.

Cancel

Closes the Integration Options tab.


Connect Dialog Box
Open Database Dialog Box

Available databases

This list shows the name and path of the databases currently available to open.  You can use the Browse button to search for a database that doesn't appear in the list.

Open

Opens the specified database, if available.

Cancel

Cancels the database connection.

Remove

Removes the database connection from the available list. (The database is not physically deleted.)


Refresh File Status (Development Environment)

Refreshes the file status display in the Visual Basic project window.

To use the Refresh File Status command

•	On the Visual Basic Tools SourceSafe menu, click SourceSafe Refresh File Status.

Remarks

Use this command when you have checked a file in or out, or want to check the project status in a multi-developer environment where other source code control users may have changed a project file's status.


Find Makefile Dialog Box

Allows you to locate a project file so you can open it under source control.

Once the project file (make file) is located, click OK to open it under source control, or click Cancel to cancel the operation.


 Properties Command (File Menu)

Displays the Properties dialog box, which contains basic information about a Visual SourceSafe file or project, including the size, name, and type.

Access Rights

You must have the Read access right to view the Properties dialog box.

You must have the Add access right to change the type of a file.

You must have the Destroy access right to change the Store Only Latest Version state of a file.

Remarks

Click the tab with the information you want.  Tab content differs according to whether a file or project is currently selected in Visual SourceSafe Explorer.

Note   Click the Report button on any of the tabs to create a report to send to the Clipboard, a text file, or a printer.

File Properties Dialog Box Tabs

General

Shows the filename, type, size, latest version number, last modification date, comment, and whether the entire file history is stored in the SourceSafe database (or just the latest version).  You can change the comment and set whether or not to store only the latest version of the file to save disk space.  You can also change the file type here.

Check Out Status

Shows the file's name, who it is checked out by (if anyone), whether it is exclusively checked out, when it was checked out, the current version, the check out path (with the computer name), the project the file is in, and the check out comment.  You can change the check out comment.

Links

Shows the current share links a file has to other projects.

Paths

Shows which projects have branched versions of this file in the past.


Visual SourceSafe

Visual SourceSafe is the leading source control tool for code and web developers.  It can store and protect any type of file.  For more information, open the Visual SourceSafe Help file on your system (if you have Visual SourceSafe installed).


Topics


Project <project> has been destroyed, and cannot be rebuilt.

See Also

Visual SourceSafe may not be able to reproduce the project version you requested.  This error has the following cause and solution:

•	You permanently destroyed a subproject or moved the subproject to another location.  For example, there may have been a subproject that you deleted or purged.  Later, you attempted to go back to an earlier version of the project.  Visual SourceSafe attempts to reconstruct the project exactly as it was in the past, but it cannot, because the subproject cannot be recovered.

Click Yes, and Visual SourceSafe does its best to restore the old project version, but restoration is not guaranteed.

Click No, and the attempt to restore an old project version is halted.

Click Yes All, and Visual SourceSafe does not notify you that other selected files may also be unrecoverable, but continues with the best possible reconstruction.


An item has been destroyed or moved, and cannot be rebuilt See Also
See Also

Purge Command

Delete Command


File <file> has been destroyed, and cannot be rebuilt.

See Also

Visual SourceSafe may not be able to reproduce the file you requested.  This error has the following cause and solution:

•	You permanently destroyed a file or moved the file to another location.  For example, there may have been a file in a project that you deleted or purged.  Later, you attempted to go back to an earlier version of the project.  Visual SourceSafe attempts to reconstruct the project exactly as it was in the past, but it cannot, because the file cannot be recovered.

Click Yes, and Visual SourceSafe does its best to restore the old file, but restoration is not guaranteed.

Click No, and the attempt to restore an old file is halted.

Click Yes All, and Visual SourceSafe does not notify you that other selected files may also be unrecoverable, but continues with the best possible reconstruction.


An item with the name <name> already exists.

See Also

Each item in a Visual SourceSafe project must have a unique name.  This error has the following cause and solution:

•	You have attempted to name a file or an immediate child project with the same name as the project.  (An item with that name can exist in other projects in the database, including subprojects.)

To resolve this error, give the new item a different, unique filename.  Or, you can delete or rename the existing item.

Note   File and project names in Visual SourceSafe are not case-sensitive.  For example, if you have a file named TEST.C, you cannot create a subproject or file named "Test.c" or "test.c" in the same project.


A file or project already exists with the name <file> See Also
See Also

Add Files Command

Delete Command

Rename Command

Share Command


File or project not found.

See Also

Visual SourceSafe is looking for a file or project that does not exist.  This error has the following cause and solution:

•	You mistyped the file or project name, or specified a file or project that does not exist.

•	The Visual SourceSafe database is corrupted. .

Try retyping the name or select the name from the list in Visual SourceSafe Explorer.  If you suspect database corruption, run the ANALYZE.EXE utility.


File or project not found See Also
See Also

Visual SourceSafe Explorer


Version not found.

See Also

The version specified cannot be found.  This error has the following causes and solutions:

•	You specified a version that does not exist.

In Visual SourceSafe, click the Show History command on the Tools menu, and then choose a version from within the History of File dialog box.

•	If you are using Visual SourceSafe from the command line, you may not be using the -V parameter properly.

Search online Help for more information on using the parameter correctly (click the Contents button).


Version not found See Also
See Also

Show History Command

Tracking Old Versions

-V Command-Line Option


This command only works on files.

This command can operate only on files.  This error has the following cause and solution:

•	You are attempting to perform a file operation (such as using the View command) on a project.

Select the proper command, or select a file that works with the command you've chosen.


This command only works on projects.

This command can operate only on projects.  This error has the following cause and solution:

•	You are attempting to perform a project operation (such as the Move Project command) on a file.

Select the proper command, or select a project that works with the command you've chosen.


Parent not found.

See Also

This error has the following cause and solution:

•	Database corruption is indicated.

Ask your  Visual SourceSafe administrator to run ANALYZE.EXE to find and correct the problem.  If that fails, call Microsoft Technical Support for help with recovering the database.


Parent not found See Also
See Also

Technical Support


<File> is not branched in <project>.

See Also

This error has the following cause and solution:

•	The file you are trying to merge is not branched.

When a file is branched, and you want to merge the different version of the file into one combined file, you can use the Merge Branches command.  In this case, the file is not branched, so Merge Branches has no effect.


Cannot move a project under itself.

See Also

A project cannot be a project of itself.  This error has the following cause and solution:

•	You attempted to create an invalid loop in your project hierarchy.  For example, moving the project $/WORD under the project $/WORD, or, more subtly, moving $/WORD under $/WORD/APPS.  This creates an endless recursive loop, which causes this error.

Restructure your project hierarchy so that there is no invalid loop.


Cannot move a project under itself See Also
See Also

Move Project Command

Projects


File not checked out by you.

See Also

Some Visual SourceSafe operations can only be performed on a file that is checked out.  This error has the following causes and solutions:

•	You attempted to check in or undo a check out on a file that you did not have checked out.

Check out the file before checking it in.  If you have made changes to a file, see the Advanced options in the Check Out dialog box, and then under Replace Writable, select Skip to check out the file to you without replacing the changes in your working folder.

•	You attempted to perform an operation that can only be performed on a file that is checked out.

Check out the file.


File not checked out by you See Also
See Also

Check In Command

Check Out Command


File <file> does not retain old versions of itself.

See Also

This error has the following cause and solution:

•	When you check in a file, Visual SourceSafe retains both the current version of the file, and the information required to rebuild past versions.  You have turned off the historical version storage for this file.

If you explicitly turn off this change information in the Properties dialog box or when using the Add Files command, Visual SourceSafe can give you the most recent version, but it cannot rebuild old versions.


File does not retain old versions of itself See Also
See Also

Check In Command

Tracking Old Versions


Invalid date string.

Visual SourceSafe cannot use the date syntax entered.  This error has the following cause and solution:

•	The date you typed or entered is invalid.

Proper date syntax is Month/Day/Year, with each number separated by a slash mark: for example, 2/29/64 or 11/5/1992.


Invalid time or date string.

Visual SourceSafe cannot use the date or time syntax entered.  This error has the following causes and solutions:

•	The date you typed or entered is invalid.

Proper date syntax is Month/Day/Year, with each number separated by a slash mark: for example, 2/29/64 or 11/5/1992.

•	The time you typed or entered is invalid.

Proper time syntax is Hour:Minute, followed by a one-letter A.M. or P.M. indicator: for example, 9:30A or 5:00p.  (The indicator is not case sensitive.)  Or, you can use a 24 hour syntax such as 13:45.


Invalid syntax on line <line> of file <file>.

See Also

This error has the following cause and solution:

•	The syntax of one or more lines in the initialization file is invalid.

Search Help for information on the proper syntax of the initialization variable.

Note   You can use any text editor to change or delete the invalid line.


Invalid syntax <syntax> in initialization file See Also
See Also

The Initialization File Variables


Initialization variable <variable> set to invalid number.

See Also

The specified initialization variable has been set incorrectly.  This error has the following cause and solution:

•	An initialization variable that should be set with an Arabic number is not.  For example, it may be set to "two" when it should be set to "2."

Search Help for information on the proper syntax of the initialization files.

Note   You can use any text editor to change or delete the invalid line.


Initialization variable <variable> set to invalid number See Also
See Also

The Initialization File Variables


Initialization variable <variable> must be between <number> and <number>.

See Also

An initialization number is out of the valid range.  This error has the following cause and solution:

•	An initialization variable has been set to an invalid number.

Search Help for information on valid settings.

Note   You can use any text editor to change or delete the invalid line.


Initialization variable <variable> must be between <number> and <number> See Also
See Also

The Initialization File Variables


Initialzation variable <variable> must be set to "Yes" or "No".
Initialization variable <variable> must be set to "Yes" or "No".

See Also

This error has the following cause and solution:

•	An initialization variable that should be set to Yes or No is not.

Change the variable so that it is set to Yes (or True) or No (or False).

Note   You can use any text editor to change or delete the invalid line.


Initialization variable <variable> must be set to Yes or No See Also
See Also

The Initialization File Variables


Initialization variable <variable> set to invalid folder path.

See Also

An initialization variable that should be set to a valid folder path is set to an invalid path.  This error has the following cause and solution:

•	The path syntax may be incorrect or the path may not exist.

Verify that the path exists or that the syntax is correct and change it as necessary.

Note   You can use any text editor to change or delete the invalid path.


Initialization variable <variable> set to invalid folder path See Also
See Also

The Initialization File Variables


Initialization variable <variable> set to invalid value.

See Also

This error has the following cause and solution:

•	An initialization variable is set to an invalid value.

Search Help for information on the proper syntax.

Note   You can use any text editor to change or delete the invalid path.


Initialization variable <variable> set to invalid value See Also
See Also

The Initialization File Variables


Cannot find initialization variable <variable>.

See Also

Visual SourceSafe cannot find an initialization variable it needs to perform an operation.  This error has the following cause and solution:

•	The specified initialization variable is missing and is required to complete the operation.

Search Help or the Microsoft Visual SourceSafe User's Guide for information on the variable, determine a proper value for it, and add it to your initialization file.


Cannot find initialization variable <variable> See Also
See Also

Configuring Visual SourceSafe


Cannot find SS.INI file.

See Also

Visual SourceSafe cannot find your SS.INI file.  This error has the following causes and solutions:

•	The SS.INI file is not where Visual SourceSafe expects to find it.  (See your Visual SourceSafe administrator if you have moved this file.)

•	You have inadvertently deleted your SS.INI file.

You can copy an SS.INI file from another user into your Visual SourceSafe folder, then modify it to customize Visual SourceSafe.  Your Visual SourceSafe administrator must then set Visual SourceSafe to look in the proper place.


Cannot find SS.INI file See Also
See Also

The Initialization File Variables


Permission denied.

This error has the following cause and solution:

•	You are attempting to take an action that you do not have the proper privileges to execute.

Talk to your Visual SourceSafe administrator.  If you are the Visual SourceSafe administrator, run Visual SourceSafe Administrator to check on or change your username, password, and access rights.


User <user> not found.

This error has the following cause and solution:

•	Your username was not found.

Talk to your Visual SourceSafe administrator.  If you are the Visual SourceSafe administrator, run Visual SourceSafe Administrator to add your username.


Invalid password.

This error has the following cause and solution:

•	Your username/password combination is invalid.

Re-enter the password.  Because it does not appear on the screen, it is very easy to type it incorrectly.  Note that the Visual SourceSafe password is case-insensitive.  If you believe you have typed the password correctly, Visual SourceSafe doesn't recognize the password for some reason, so ask your Visual SourceSafe administrator to change your username and password.  If you have forgotten your password, the administrator can use Administrator to assign you a new one.


Bad username syntax: <syntax>.

This error has the following cause and solution:

•	You have entered a username with invalid Visual SourceSafe user syntax.

Ask your SourceSafe administrator for your correct Visual SourceSafe username.


Invalid SourceSafe syntax: <syntax>.

See Also

The syntax you entered is invalid in Visual SourceSafe.  This error has the following cause and solution:

•	You have entered a Visual SourceSafe file or project path that does not use valid syntax.

In Visual SourceSafe syntax, every path starts with a dollar sign followed by a series of project names, which are separated by slashes and optionally followed by a filename.  For example:

•	$/ is the root project.

•	$/CODE is a subproject of $/.

•	$/CODE/WIN/TEST.C is a file in the $/CODE/WIN project.

Many parts of this syntax are optional.  You can omit the dollar sign in most circumstances.  You can also shorten the path by basing it on your current project; for example, if you are in $/CODE, you can type WIN as a shorthand for $/CODE/WIN, TEST.C for $/CODE/TEST.C, and ".." for the root.

Filenames are any valid operating system filenames; project names can include spaces and can be up to 256 characters long.  Project names are not case-sensitive (for example, to Visual SourceSafe, Code and CODE are the same project).


Invalid SourceSafe syntax See Also
See Also

SourceSafe Naming Syntax


This command operates on only one item.

For many Visual SourceSafe dialog box lists, you can choose more than one item at once, and then act on all the items together.  Some actions, however, cannot operate on more than one item at a time.  This error has the following cause and solution:

•	You selected more than one item and then applied a command that operates on only one item at a time.  For example, you may have tried to use the View command, which works with one file at a time.

Press the space bar on an item to make it the only item selected in the list.


You cannot use wildcards with this command.

Many Visual SourceSafe commands accept wildcard characters, such as * and ?.  But some commands, such as the View command, can operate on only one item at a time.  This error has the following cause and solution:

•	The command you have chosen does not accept wildcard characters.

Use an explicit filename, with no wildcard characters.


No items listed to operate on.

This error has the following cause and solution:

•	You are attempting to perform an action without first selecting an item to operate on.

Click an item to select it, and then try the action again.


Network not found.

This error has the following cause and solution:

•	No network is installed, or Visual SourceSafe cannot find a valid network.

Perhaps there is no network installed, or one or more network connections have failed. Check your network hardware, and make sure that all the necessary network drivers are running.  Check with your Visual SourceSafe administrator for additional assistance.


<File> is an invalid or corrupted logfile.

See Also

This error has the following cause and solution:

•	Visual SourceSafe cannot find or read your logfile.

Run ANALYZE.EXE with the -F option.  If necessary, check with Technical Support for more assistance.


<File> is an invalid or corrupted logfile See Also
See Also

Technical Support


Corrupted history in file <file> after revision <number>.

This error has the following cause and solution:

•	The Visual SourceSafe database has been corrupted.

DDCONV.EXE saves as much of the database as possible, but some information will be irretrievably lost (unless you have backed up the database and can recover the information from there.)


Illegal file or project name(s): <file>".

See Also

This error has the following cause and solution:

•	You have entered an illegal file or project name.

Check to make sure that the name was entered correctly.  If you are unsure which characters are allowed in a SourceSafe name, check the Visual SourceSafe Naming Syntax and Conventions topic.


Invalid network path <path> See Also
See Also

Visual SourceSafe Naming Syntax and Conventions


Illegal version syntax: <number>.

This error has the following cause and solution:

•	The version number you entered uses illegal syntax.

Check to make sure that the information was entered correctly.


An item named <item> was already deleted from this project.

See Also

In Visual SourceSafe, you can delete only one instance of a file or project with a given name in a given project.  This error has the following cause and solution:

•	You deleted a file, created a new file with the same name, and then attempted to delete that file as well.

You can choose Yes to purge the old file, or No to cancel the delete operation.  If you purge the original file, you will lose all historical information in it, but you can then continue with the current delete operation.  Or, you can choose No, and then rename the new file before deleting it, if you want to keep the file history of the old file.


The item was already deleted from this project See Also
See Also

Purge Command

Delete Command

Rename Command


Cannot delete, rename, or move the root project.

This error has the following cause and solution:

•	The Delete, Rename, and Move Project commands cannot be applied to the root project ($/), which is analogous to the root folder of your hard disk (C:\).

Since the root project cannot be changed in any way, consider restructuring your project.


<file> is already checked out by <user>.  Continue?

See Also

This warning has the following cause and solution:

•	You attempted an operation on a Visual SourceSafe file that is checked out by another user.

Visual SourceSafe gives you the option to continue, which means any differences between the changes you make to the file and the changes made by the other user will need to be merged in the future.  Click Yes to continue your operation and create a multiple-checkout situation; answer No to cancel the check out action.


File is already checked out.  Delete anyway? See Also
See Also

Check Out Command

Destroy Command

Delete Command


Rename does not move an item to another project.

See Also

The Rename and Move Project commands cannot be implemented at the same time.  This error has the following cause and solution:

•	The Visual SourceSafe Rename command and Move command are separate, distinct operations; you cannot do both in one step.

First perform one action and then do the other.


Rename does not move an item to another project See Also
See Also

Move Project Command

Projects

Rename Command


File <file> is currently checked out by <user>.

See Also

This error has the following cause and solutions:

•	When someone other than you has a file checked out, there are some things you cannot do to the file.  For instance, you cannot delete or rename a file that is checked out.

Click Yes to check out the file anyway.  (Yes All checks out all selected files even if they are already checked out by another user.)  If you choose yes, there may be conflicts between your changes and those of another user, which will have to be resolved and merged later.

Click No to cancel the Check Out command.  (No All cancels the command for all selected files.)

If you want to work on a checked-out file, it's best to check the User column of SourceSafe Explorer for the name of the user who has it checked out and ask that user to check it in as soon as possible.  If the user is unavailable, the Visual SourceSafe administrator can undo the check out for you.


File <file> is currently checked out by <user> See Also
See Also

Undo Check Out Command


Cannot rename to <file>; that name already exists.

See Also

The filename specified already exists in the project.  This error has the following cause and solution:

•	When you rename a file that is shared by many different projects, the name of the file changes in all the projects that are sharing it.  If any one of these projects already has a file with the same name, you create an ambiguous and invalid situation, two files in the same project with the same name, and the Rename operation fails.

To correct this, choose another name for the file.


Cannot rename to <file>; that name already exists See Also
See Also

Rename Command

Shared Files


Project <project> does not exist.

This error has the following cause and solution:

•	You are attempting to move a project to a parent project that does not exist.

Check the path of the parent project and try again.  If you are unsure of Visual SourceSafe project syntax, try selecting the parent from the project list in SourceSafe Explorer, and then note the project path displayed above the file list.

Note   To move a file or subproject to a new parent, you must have already created the new parent project.  Use the Create Project command to create a new project.


Path <path> too long.

See Also

The path specified is too long.  This error has the following cause and solution:

•	You typed a Visual SourceSafe path that is too long.

Visual SourceSafe project names are limited to 64 characters.  Full project path names can be no longer than 255 characters.


Path <path> too long See Also
See Also

SourceSafe Naming Syntax


This version of <name> already has a label: overwrite?

Any version of a Visual SourceSafe file or project can have a label, which is used to identify that version.  This error has the following cause and solution:

•	One version of a file or project cannot have more than one label.  Therefore, when you attempt to label a version that already has a label, Visual SourceSafe displays this message.

Click Yes to apply the new label, and the old label is replaced.  Click No to cancel the action, and the old label is left in place.


This label <label> is already used.  Remove the old label?

A Visual SourceSafe label is used to identify a particular version of a file or project.  This error has the following cause and solution:

•	You are attempting to assign a label to a file or project, and another version of that file or project has the same label.

Click Yes, the new label is applied, and the old label is deleted. Click No, and the old label is not changed.  Click Cancel to cancel the labeling operation.


File <file> is already shared with this project.

See Also

This error has the following cause and solution:

•	You are attempting to share a file with the current project, and that file already exists in the current project.

If you want to share a different version of the file, specify a version in the History of File dialog box and click Pin.  If you want to share this file with another project, select the project to share the file into in Visual SourceSafe Explorer and on the SourceSafe menu, click Share. Then, select the file to share from the Share dialog box.


File is already shared with this project See Also
See Also

Show History Command

Shared Files

Tracking Old Versions

-V Command Line-Option


Cannot check out an old version of a file.

See Also

The Check Out command always uses the most recent version of a file.  This error has the following cause and solution:

•	You are trying to check out an old version of a file.

If you want to use and modify a previous version, take the following steps:

1.	Check out the most recent version of the file.

2.	Delete it from your working folder (not the Visual SourceSafe database).

3.	Get the old version that you want to modify.

4.	Make your changes to the old version.  (This may require removing its read-only flag manually.)

5.	Check the modified file into Visual SourceSafe.

Note   You can also use the Rollback button in the History of File dialog box (on the Tools menu, click Show History).  If you roll back to a certain version, all versions subsequent to that version are deleted, and you can check out the file and start modifying it.  The disadvantage of this method, however, is that you lose all the subsequent versions, and cannot retrieve them.


Cannot check out an old version of a file See Also
See Also

Check In Command

Check Out Command

Get Latest Version Command

Rollback Command


File <file> is checked out to project <project>, and you are in <project>.

When a file is shared among multiple projects, a file in one project is linked to all other projects that share it.  Therefore, when you check out the file from one project, it is also checked out from all the projects that share it.  This warning has the following cause and solution:

•	You checked out a file from one project, and you are attempting to check the file in or undo the checkout from another project that shares the same file.

This is a valid action [image] Visual SourceSafe is simply alerting you in case this is not what you intend.  To proceed, click Yes; to cancel the operation, click No.

Note   You can check in a file or undo a checkout from any project that shares a file.


File <file> was checked out to folder <path>.

When you check out a file, Visual SourceSafe keeps track of the working folder you checked it out to.  In general, you make your modifications in that folder, and then check in the file or undo the checkout from the same folder when you are done.  This warning has the following cause and solution:

•	You are attempting to check in or undo a checkout of the file from a folder different from the one you checked it out to.

Your working folder for a project is displayed just above the file pane in SourceSafe Explorer, and can be changed with the Set Working Folder command from the File menu (CTRL+D); the check out folder of a file is displayed in the file list.  (The check out folder may be different from your working folder assigned to the project, if someone else has the file checked out, for example.)  Although you can check a file in from a folder other than the one you checked it out to, make sure that this is what you intend.


File <file> has not been changed.

This error has the following cause and solution:

•	You are attempting to check in a checked out file that you have not changed.

Click Yes, and Visual SourceSafe checks it in anyway.  (Clicking Yes All checks in all selected files.)  A check in creates a new version of the file, with an optional comment.

Click No, and Visual SourceSafe undoes the check out of the file.  (Clicking No All undoes the checkout for all selected files.)  No new version of the file is created in this case.

Note   To avoid this message on future occasions, you can turn off this notification on the General tab in the SourceSafe Options dialog box on the Tools menu.


A writable copy of <file> already exists.

When you get a Visual SourceSafe file, the file is tagged with the read-only flag [image] you cannot modify the file.  When you check out the file for modification, the read-only flag is deleted.  When you later check it in, the file is flagged read-only again.  This error has the following cause and solution:

•	You attempted to use the Get Latest Version command on a file that already exists on your hard disk in writable form.  If the local copy is writable, you may have it checked out, or are otherwise modifying it; Visual SourceSafe does not replace the file, and displays this error message.

Click Yes or Yes All to replace the file or files with the current version is the Visual SourceSafe database.

Click No or No All to not replace the file or files.

Click Cancel to cancel the Get Latest Version command.


File <file> is not shared with any other projects.

The Branch command is used to break a share link.  This error has the following cause and solution:

•	The file you've chosen to apply the Branch command to has no link to other projects.

Choose another command, or choose a shared file to apply the Branch command.


You are using an old version of <file>, and cannot change it.
You are using an old version of <file>, and cannot change it.  Rollback to make that version the most recent if you need to change it.

See Also

This error has the following cause and solution:

•	You tried to modify an old version of a file.

If you want a project to always use a specific version, and not receive checked in changes made in other projects, you can share a specific version of the file using the Pin command in the History of File dialog box.

If you want to start modifying the file from an old version, you can roll back the file.  The Rollback command only affects the current project; it performs an implicit separate operation.  Both branching and roll backs are available from the History of File dialog box.


You are using an old version of <file>, and cannot change it. See Also
See Also

Rollback Command

Tracking Old Versions


Cannot roll back to the most recent version of <file>.

See Also

The Rollback command returns a file to a previous version of itself.  This error has the following cause and solution:

•	You have attempted to roll back a file to its most recent version or have not specified a version to roll back to.

You cannot roll back a file to the current version in Visual SourceSafe. If you meant to specify an earlier version, retry the command with the earlier version specified.


Cannot roll back to the most recent version of <file> See Also
See Also

Rollback Command


A deleted link to <file> already exists.

See Also

A deleted file remains part of a project, but it doesn't appear in the file list.  This error has the following cause and solution:

•	You are attempting to share a file from another project with the current project.  However, the file already exists in the current project.  It doesn't appear in the file list because it has been deleted.

To make the file appear in the file list, don't share it from another project; rather, recover it in this one using the Recover button on the Deleted Items tab in the Properties dialog box (File menu).


A deleted link to <file> already exists See Also
See Also

Recover Command

Delete Command

Shared Files


Folder <path> not found. Create?

The specified working folder does not exist.  This error has the following cause and solution:

•	The folder may have been deleted, or you may have entered its specification incorrectly.  Your network connection to a networked location may also have gone down.

Reset the working folder for this project (using the Set Working Folder command on the File menu), or click Yes to create the folder.  This tells Visual SourceSafe that this is the local working folder.  When you open the project again, Visual SourceSafe automatically goes to this working folder.

If your working folder seems fine, check to see if this project is shadowed to another location, and that your connection to that location is still OK.


<item> specifies a version number, which is illegal for this command.

This command operates only on the most recent version of a file.  This error has the following cause and solution:

•	You attempted to execute the command on an older version of the file.

Choose another command, or apply the command you've chosen to the most recent version of the file.


This command operates only on projects, not on files (like <file>).

This command operates only on projects.  This error has the following cause and solution:

•	You attempted to execute the command on a file.

In the SourceSafe Explorer, select a project in the project list, then try the command again.


This command operates only on files, not on projects (like <project>).

This command operates only on files.  This error has the following cause and solution:

•	You attempted to execute the command on a project.

In the SourceSafe Explorer, select a file in the file list, then try the command again.


<file> is not a text file.

Although most Visual SourceSafe commands work on either text or binary files, this command does not.  This error has the following cause and solution:

•	You attempted to execute a command, such as View File on the Edit menu or Find In Files on the Tools menu, that operates only on text files.

Binary file types are set either automatically by Visual SourceSafe or manually using the File Types tab in the SourceSafe Options dialog box (Tools menu).


Invalid Visual SourceSafe path <path>.
Invalid SourceSafe path <path>.

See Also

This error has the following cause and solution:

•	You have entered an invalid Visual SourceSafe project or filename.

Check to make sure that you typed the path correctly, or use Visual SourceSafe Explorer to choose the item from the project list or file list.

If you chose the item from Visual SourceSafe Explorer, it is possible that another user has deleted or renamed the item since you last used Visual SourceSafe.  Collapse the root project and re-expand it to refresh the project pane.


Invalid Visual SourceSafe path <path> See Also
See Also

Delete Command

Rename Command


 <item> is not a deleted file or project.

See Also

The Recover and Purge commands operate only on items that have been deleted.  This error has the following cause and solution:

•	You attempted to use the Recover or Purge command on an item that has not been deleted.

If you are trying to recover a file or project, there is no need, as the file or project already exists in Visual SourceSafe.  To view the file, use the View File command.


<item> is not a deleted file or project See Also
See Also

Delete Command

Destroy Command

Purge Command

Recover Command


<item> has been deleted.

See Also

This error has the following cause and solution:

•	You are trying to act on a file or project that has been deleted in the current project.

Before you can do anything to the file, you must recover it using the Recover command.

If you want to delete the file from the Visual SourceSafe database permanently, on the File menu, click Properties, and then on the Deleted Items tab, click Purge.


<item> has been deleted See Also
See Also

Purge Command

Recover Command

Delete Command


<File> is checked out by <user>; deleting it will cancel the check out.  Continue?

This warning has the following cause and solution:

•	You are attempting to delete a checked out file.

This warning provides the opportunity to correct from deleting the wrong file. If the filename is correct, click Yes to proceed. Click No to cancel the delete operation.


Destroy cannot be undone; information will be lost permanently!

See Also

This warning has the following cause and solution:

•	When you use the Destroy command on a file or project, the action is not reversible.

Click Yes to continue with the Destroy operation. Click No to cancel the operation.

Note   If you do not want to receive this message every time you destroy a file or project, you can turn it off on the Warnings tab in the SourceSafe Options dialog box (Tools menu).


Destroy cannot be undone; information will be lost permanently! See Also
See Also

Destroy Command

Purge Command

Delete Command


Delete all specified items?

See Also

This warning has the following cause and solution:

•	You are about to delete a file or project.

Click Yes, and Visual SourceSafe deletes the file or project.

Click No, and Visual SourceSafe does not.

Use the Recover command to undo Delete.

Note   If you do not want to receive this message every time you delete a file or project, you can turn it off on the Warnings tab in the SourceSafe Options dialog box (Tools menu).


Delete all specified items See Also
See Also

Recover Command


Purge cannot be undone; information will be lost permanently!

See Also

This warning has the following cause and solution:

•	When you purge a file or project, the action is not reversible.

Click Yes to continue with the Purge operation. Click No to cancel the operation.

If you do not want to lose the file or project permanently, use the Delete command instead.

Note   If you do not want to receive this message every time you delete a file or project, you can turn it off on the Warnings tab in the SourceSafe Options dialog box (Tools menu).


Purge cannot be undone; information will be lost permanently! See Also
See Also

Destroy Command

Purge Command

Delete Command


Rollback cannot be undone; some versions will be lost irretrievably!

See Also

This warning has the following cause and solution:

•	You are about to roll back a file to an earlier version.  The Rollback command is not reversible.

To make the old version the most recent version without losing all the versions in between:

1.	Check out the file.

2.	Delete the local copy.

3.	Get the version you want to roll back to.

4.	Check that version into Visual SourceSafe.

Note   If you do not want to receive this message every time you roll back a file, you can turn it off on the Warnings tab in the SourceSafe Options dialog box (Tools menu).


Rollback cannot be undone; some versions will be lost irretrievably! See Also
See Also

Rollback Command


$ <file> has changed.  Undo check out and lose changes?
<file> has changed.  Undo check out and lose changes?

See Also

This warning has the following cause and solution:

•	You are about to undo the check out of a file.  If you do so, you discard all the changes made since you checked out the file.

If you want to put your changes into Visual SourceSafe instead of losing them, use the Check In command instead.

Note   If you do not want to receive this message every time you undo a checkout on a file, you can turn it off on the Warnings tab in the SourceSafe Options dialog box (Tools menu).


Undo the check out of all specified items? See Also
See Also

Check In Command

Undo Checkout Command


This will end your Visual SourceSafe session.
This will end your SourceSafe session.

This message has the following cause and solution:

•	You are about to exit Visual SourceSafe.

Click OK to exit Visual SourceSafe, or click Cancel to return to Visual SourceSafe.

Note   If you do not want to receive this message every time you exit, you can turn it off on the Warnings tab in the SourceSafe Options dialog box (Tools menu).


There are no deleted items in this project.

This error has the following cause and solution:

•	There are no items in this project that have been deleted.

Because no files have been deleted from this project, there are no files that you can recover or purge.


The files are identical.

This message has the following cause and solution:

•	The files you have selected, the Visual SourceSafe master copy and the local copy, are identical.  You may have selected a file in the file list and tried to run the Show Differences command only on that file, in which case the file is being compared to itself and is by definition identical.

In this case, before applying the Show Differences command again, specify two distinct files.


No search pattern was given.

This error has the following cause and solution:

•	You have not entered a string or pattern that Visual SourceSafe can use to search through files.

Enter a string in the Find In Files dialog box and then click OK, or click Cancel to exit the dialog box and return to Visual SourceSafe Explorer.


No matches were found.

This error has the following cause and solution:

•	Visual SourceSafe has searched all the selected files, and has found no occurrences of the string you are trying to find.

Check to make sure that you've entered the string correctly.


Always share the latest version of <file>?

See Also

Generally, every project sharing a file always has the latest version of the file.  When you check in the file in any project, all the projects are automatically updated.  However, you can use the Pin button in the History of File dialog box to share an explicit version of a file.  This message has the following cause and solution:

•	By clicking the Pin button in the History of File dialog box, you've chosen to share the most recent version of the file.

If you click No, the project shares the pinned version explicitly, and does not receive checked-in changes from other projects.

If you click Yes, the project returns to a sharing state in which it is always using the latest version of the file.


Always share the latest version? See Also
See Also

Pin Command

Shared Files

Tracking Old Versions

Unpin Command


You must specify a new name.

This error has the following cause and solution:

•	You are attempting to rename a file or project without specifying a new name for it.

Either specify a new name and then click OK, or press the ESC key to close the dialog box without renaming the file or project.


Binary files differ.

This message has the following cause and solution:

•	The binary files you've selected differ.

The Show Differences command does not display line-by-line differences for binary files.  Therefore, Visual SourceSafe can only tell you whether or not the Visual SourceSafe master copy is different from your local copy.


The passwords don't match.

This error has the following cause and solution:

•	The password you typed in the Password box does not match the one typed in the Verify box.

If the passwords you type are identical, Visual SourceSafe assumes you typed them correctly, and changes your password.  If you type two different passwords, Visual SourceSafe assumes that you mistyped the password; you must re-enter it.


Get the entire project containing this file version?

See Also

This message has the following cause and solution:

•	You have selected a file in the History of File dialog box list and then clicked Get.

Click Yes, and Visual SourceSafe gets the entire project as it existed immediately after the selected file was checked in.

Click No, and Visual SourceSafe gets only the file version you selected, but doesn't get any other files in the project.


Get the entire project containing this file version? See Also
See Also

Get Latest Version Command


Running more than one instance of the SourceSafe Explorer or the SourceSafe Administrator is not supported under 16-bit Windows.

This error has the following cause and solution:

•	You can run only one version of SourceSafe at a time on a 16-bit platform.

Do not try to run a second instance of Visual SourceSafe.  Running multiple instances of Visual SourceSafe is supported under Microsoft Windows NT and Microsoft Windows 95.


File <file> not found.

Visual SourceSafe could not find the file it was looking for.  This error has the following cause and solution:

•	You may have mistyped a filename in Visual SourceSafe Explorer or in an initialization file variable.

•	The file may not exist.

Make sure that you've correctly entered the name of the file.


Too many file handles open.

This error has the following cause and solution:

•	There are too many files open on your system.

You may want to check whether any of the files can be closed, or you may want to increase the Files count in your operating system's initialization file.


Access to file <file> denied.

At certain times, Visual SourceSafe denies a user access to a file.  This error has the following causes and solutions:

•	You were denied access (read or write privileges) to a file that Visual SourceSafe was attempting to open.

It is possible that another user has the file momentarily locked; try again.

•	You may not have sufficient network privileges to take the action you are attempting.

See your Visual SourceSafe administrator for more information on your Visual SourceSafe access rights.  Also see the Administration chapter of the Microsoft Visual SourceSafe User's Guide for a description of the network access rights required for various users in different directories.


Invalid drive: <drive>.

This error has the following cause and solution:

•	The drive you are attempting to access is invalid.  You may have mistyped the drive specification, either in Visual SourceSafe Explorer or in an initialization file.

Check to make sure that you've entered the correct the drive specification.


File <file> already exists.

This error has the following cause and solution:

•	You tried to create a file or folder with a name that already exists.

You can give Visual SourceSafe files the same name as many times as you want in different directories, but only once in a given folder.  Select a different name or rename the conflicting file or project.


Disk full.

This error has the following cause and solution:

•	You tried to save data to a full disk.

Free some disk space by deleting or moving unneeded files.


Invalid filename: <file>.

This error has the following cause and solution:

•	You typed a filename with invalid syntax.

Check your typing, or select a different name with valid characters. You may also get this error if you have multiple files selected and try to use a command meant for a single file, such as View.


Error reading from file.

Visual SourceSafe cannot read from a file it has opened.  This error has the following cause and solution:

•	You may have lost your network connection.

Exit Visual SourceSafe, and then check all network connections before restarting.


Error writing to file.

Visual SourceSafe cannot write data into a file that it has opened. This error has the following cause and solution:

•	You may have a full disk.

Exit Visual SourceSafe, and then free disk space by deleting unnecessary files.


Out of memory.

You do not have sufficient computer memory to perform this operation.  This error has the following cause and solution:

•	You have too many applications, documents, or source files open.

Close any unnecessary applications, documents, or source files that are open.

•	You have many device drivers loaded.

Eliminate unnecessary device drivers.


You have <file> checked out; deleting it will cancel the check out.

This warning has the following cause and solution:

•	You are attempting to delete a file checked out to you.

This warning provides the opportunity to avoid deleting the wrong file.  If the filename is correct, click Yes to proceed.  Click No to cancel the delete operation.


Folder not found.

This error has the following cause and solution:

•	You specified a operating system folder that could not be found.

Check to make sure that the folder specification is correct. Check capitalization on case-sensitive operating systems, and re-try.


Cannot find Help file <file>.

See Also

This error has the following cause and solution:

•	The Help file isn't available.

Try reinstalling Visual SourceSafe to get a copy of the Help file.  If the file is still missing, call Technical Support.


Cannot find Help file <file> See Also
See Also

Technical Support


Too many file handles open.

This error has the following cause and solution:

•	You have too many files open at once..

Close some open files.


File <file> is locked.

This error has the following cause and solution:

•	The file you are trying to access is already being used.

Wait and try your operation again later.


An automatic merge has occurred and there are conflicts.  Edit <file> to resolve them.

See Also

Changes you made to the file since you checked it out conflict with other changes made (and checked in) to the source file by another user.  This error has the following cause and solution:

•	You have to resolve the conflicts between your changes to a file and another user's changes before you can check in the file.

Open the file in your working folder and search for six consecutive equal signs (======).  Visual SourceSafe uses these to mark the location of a conflict.

You may prefer to use the Visual Merge feature to make conflict resolution easier.  To keep this situation from arising again, your Visual SourceSafe administrator can disable multiple check outs in your project.


An automatic merge has occurred and there are conflicts See Also
See Also

Resolving Conflicts


You do not have access rights to <command name>.

This error has the following cause and solution:

•	Your Visual SourceSafe access rights are insufficient for the command you are attempting to execute.  For example, if you are a read-only user, you can use the Get Latest Version command to view files, but you cannot use the Check Out command to modify them.

If you believe you have received this message in error, contact your Visual SourceSafe administrator.


Version <NUMBER> is identical to version <NUMBER> of <file>.

This error has the following cause and solution:

•	The two versions you are comparing are identical.

Check to make sure that the two versions are the ones you want to compare.


No additional Help is available on this item.

See Also

•	No more information is available on this dialog box.  If the cause of the problem is not clear from the message, please call Technical Support for more assistance.


No additional Help is available on this item See Also
See Also

Technical Support


User <user> already exists.

This error has the following cause and solution:

•	You attempted to add a user with a username that already exists.  You may want to choose another name; for instance, if there is already a Joyce, add JoyceF.

Note that names are not case-sensitive, so if you already have a Joyce, adding JOYCE generates this error.


Cannot delete/rename/edit the Admin user.

This error has the following cause and solution:

•	You attempted to delete, rename or change the Admin user.  The Visual SourceSafe administrator must always exist in your Visual SourceSafe Administrator user list, although you should not use Admin as an actual user.

You can, however, change the Admin user's password, used to logon to Visual SourceSafe Administrator.


Cannot check out <file>. It is binary and is already checked out.

This error has the following causes and solutions:

•	The file you specified is binary and already checked out.  Visual SourceSafe does not allow multiple check outs of binary files, because their changes cannot be merged.

Wait to check out the file until after the other user has checked it back in.


Are you sure you want to delete?

This message has the following cause and solution:

•	This is the standard delete warning displayed by Visual SourceSafe.

Click Yes, and Visual SourceSafe deletes the item(s).

Click No, and Visual SourceSafe cancels the delete command.


Filter string exceeds the maximum length of <number>.

This message has the following cause and solution:

•	The combined length of the filter values on the File Types tab in the SourceSafe Options dialog box (Tools menu) are too long.

SourceSafe uses the File Types Included in File Group field to create a filter string for the Share and Add Files dialog boxes.  This error occurs when the combined length of the file groups are too long.  The total buffer length is 511 characters.  To correct this error, shorten your file type lists.


Invalid value <value> on File Types tab.

This message has the following cause and solution:

•	You have attempted to create a file type using invalid characters.

File Type names cannot contain the following characters:[ ] ( ) , ;.  The value for a file type is a search pattern, and may not contain invalid characters.  Also, you cannot leave the "File type included in this group" edit box blank [image] some file types must be entered.


No application is associated with this file type.

This message has the following cause and solution:

•	You have attempted to view a file for which no file association exists.

This error is usually caused by trying to view a binary file. Check that you have selected the correct file, and if you have, associate an editing program with this file extension by using either the Windows95 Explorer or the File Manager.


Have the conflicts in <file> been properly resolved?

This message has the following cause and solution:

•	You have attempted to check in a file changed from the current version stored in SourceSafe .

This warning message often is displayed when you have checked out the same file to more than one user or computer. It is displayed so you can be sure that any merge conflicts have been resolved. In some cases, this warning may be displayed even if no merge conflicts occurred, and that is potentially confusing. But, if this is the case, just click Yes and continue with your work.

If there were conflicts, and you did not open the source file to resolve them, click No and do so now. When finished, re-try your Check In operation.


The passwords do not match.

See Also

This error has the following cause and solution:

•	The password you entered for the user did not match.

When changing a password for a user, you must type the new password twice to guard against typing errors. In this case, the passwords you typed did not match. Try typing them again.


The passwords do not match See Also
See Also

Technical Support


Out of memory - the rights changes could not be saved.

You do not have sufficient computer memory to perform this operation.  The changes you made to the user's rights have not been saved.

This error has the following cause and solution:

•	You have too many applications, documents, or source files open.

Close any unnecessary applications, documents, or source files that are open.

•	You have many device drivers loaded.

Eliminate unnecessary device drivers.


Path <path> does not exist.

This message has the following cause and solution:

•	You have attempted to open a file for which the specified path does not exist.

Check the path and try re-typing it again. Make sure you are on the computer to which the path applies.


You cannot change the Admin name or access privileges.

This message has the following cause and solution:

•	You have attempted to change the Admin user's name or access privileges.

The Admin user's name and access rights cannot be changed. Select another user on which to use this command.


Cannot edit the Admin user.

This message has the following cause and solution:

•	You attempted to edit the Admin user's access rights.

The Admin user's name and access rights cannot be changed. Select another user on which to use this command.


The editor '<editor>' was not found.

This message has the following cause and solution:

•	You have attempted to view or edit a file for which the specified editor could not be found. (Editor associations to file extensions are set on the General Options tab.)

Click Yes if you would like to specify a different editor. Click No to cancel the editing operation.


Editor path is a required field when prompting by editor is selected.

This message has the following cause and solution:

•	When you check the Use Editor to Prompt for Comments checkbox, you must specify the editor to use.

Set the path in the Editor field of the Command-Line Options tab of the Tools Options dialog box.


The folder '<folder>' already exists.

Each item in a Visual SourceSafe project must have a unique name.  This error has the following cause and solution:

•	You have attempted to name a file or an immediate child project with the same name as the project.  (An item with that name can exist in other projects in the database, including subprojects.)

•	You are using both a 16-bit version and a 32-bit version of Visual SourceSafe for the same project and filenames are not being mapped accurately.

To resolve this error, give the new item a different, unique filename.  Or, you can delete or rename the existing item.

Note   File and project names in Visual SourceSafe are not case-sensitive.  For example, if you have a file named TEST.C, you cannot create a subproject or file named "Test.c" or "test.c" in the same project.


There are no items in the list.

This error has the following cause and solution:

•	You specified a history operation where no items met the specified criteria.

Examine the check boxes in the history options dialog box, and make sure they are set correctly.


Label comment is invalid when no label specified.

This error has the following cause and solution:

•	You specifed a comment for a label  but no label was supplied.

If you want to label a file or project, and wish to include a comment, you must specify the label as well as the comment.


This command cannot complete without a specified working folder.

This error has the following cause and solution:

•	You choose a command that requires a working folder, without having set a working folder.

Choose OK to set a working folder for the current project now, or Cancel to cancel the command. You can also set a working folder at any time by selecting the project and then choosing the Set Working Folder command from the File menu.


No application is associated with this file type.

This error has the following cause and solution:

•	You choose to view a file for which a file association doesn't exist.  Without this association, SourceSafe doesn't know which editor to use to display the file.

Use File Manager to add an association from this file to the appropriate editor, then try your command again.

If you want to override the File Manager association for a specific file type, you can enter specific associations in your SS.INI file, for example:

.C = C:\VC\VC.EXE

.FRM = C:\WINDOWS\NOTEPAD.EXE


Set <folder> as your personal working folder for the project <project>?

This message has the following cause and solution:

•	You need to establish a working folder for all of your projects. This message is giving you the option to create the working folder immediately, rather than having to create it later using the Set Working Folder command on the File menu.

Click Yes to set the working folder for this project. Click No to skip this step for now.


Rollback is not allowed before a pinned version.

This message has the following cause and solution:

•	You tried to roll back a file to a version before the one it is pinned to.

A pinned file cannot be rolled back to a version previous to the version it is pinned to.  To rollback the file, unpin it first, then do the rollback.


<file> is a Explorer link file.
<file> is an Explorer link file.

This message has the following cause and solution:

•	You dragged a .LNK file into Visual SourceSafe.

When you drag a .LNK file into Visual SourceSafe, SourceSafe needs to determine if you want the .LNK file itself added to the database, or the file the .LNK file points to. If you want to add the file referred to by the .LNK file, click Yes. Otherwise, click No.


Could not find the file referred to by shortcut <file>.

This message has the following cause and solution:

•	The file refered to by this .LNK file could not be found.

Check that the file has not been moved or deleted. Click OK to accept and retry.


File <file> was checked out to <project>, not to <project>.
File <file> was checked out to <folder>, not to <folder>.

This message has the following cause and solution:

•	The file you are checking in was checked out in a different folder.

When dragging a file to check in, you must check it in from the folder where it was checked out. The file you dragged will not be checked in.  If you want to check the file in from this folder, use the Visual SourceSafe Check In command from the SourceSafe menu.


<type> is not a valid mask.

This message has the following cause and solution:

•	You specified an invalid mask in the Tools Options File Types tab.

You must specify a * or ? character in your file mask, and you cannot have any illegal characters such as ( , ) [ ] in the mask.

Retype the file mask using legal characters.


# All conflicts have been resolved, would you like to save the file?
All conflicts have been resolved, would you like to save the file?

This error has the following cause and solution:

•	You have successfully resolved all merge conflicts.

Choose Yes to save the file, or choose No to discard your changes.


Some conflicts have not been resolved, would you like to save the file anyway?

This error has the following cause and solution:

•	Not all the conflicts in the merged file have been resolved.

Choose Yes to save the unresolved file, or no to discard your changes and exit.


Cannot difference the specified item <item>.

This error has the following cause and solution:

At least one of the items you selected to compare with another item cannot be differenced by Visual SourceSafe.


No deployment path has been setup for <project>.

This error has the following cause and solution:

•	You tried to Deploy a project without specifying a deployment path for the project in the Administrator program.

Ask your Visual SourceSafe administrator to set up a deployment path for your web project.


The address <address> is not a valid FTP address.

This error has the following cause and solution:

•	You specified an invalid FTP address.

Re-type the address, checking for misspellings and correct addressing.


Unable to open a connection to the FTP host <host>.

This error has the following cause and solution:

•	Visual SourceSafe was unable to open a connection to the specified FTP host.

Check your network connections, and check to be sure you entered the correct syntax for your FTP host.  This error could also be caused if your FTP host is not available at this time.


Unable to deploy <project> to the FTP host <host>.

This error has the following cause and solution:

•	Visual SourceSafe was unable to open a connection to the specified FTP host and deploy your project.

Check your network connections, and check to be sure you entered the correct syntax for your FTP host.  This error could also be caused if your FTP host is not available at this time.


No differences were found for project <project>.

This error has the following cause and solution:

•	You compared two items with no differences.

This is an informational message to tell you that no differences were found between the compared items.


WARNING: If you do not use a password, others will be able to log into this SourceSafe account.
WARNING: If you do not use a password, others will be able to log into this SourceSafe account. Proceed with no password?

This error has the following cause and solution:

•	You attempted to log on without specifying a password.

This is an informational warning to make sure you want to proceed without setting a password on your account.  Choose Yes to log on, or No to cancel.


Unable to launch the web browser for page <file>.

This error has the following cause and solution:

•	Visual SourceSafe was unable to start your web browser.

Check that your web browser is functioning normally.  You may need to re-install the browser to verify your registry settings.


Remove <database> from your Database list?

This error has the following cause and solution:

•	You are deleting a Visual SourceSafe database entry from your Open SourceSafe Database list.

Choose Yes to delete the specified entry, or No to leave the database entry on the list.


<database> is already in your database list.
<database> is already in your database list. Would you like to rename it?

This error has the following cause and solution:

•	You are renaming a Visual SourceSafe database entry in your Open SourceSafe Database list.

Choose Yes to rename the specified entry, or No to leave the database entry as it is on the list.


The Database <database> does not exist, would you like to search for it?

This error has the following cause and solution:

•	You are trying to find a database that does not exist.

Choose Yes to browse for the correct Visual SourceSafe database, or No to cancel the operation.


You must enter a filename with no path for the Site map.

This error has the following cause and solution:

•	You tried to specify a file path for the site map file.

The site map file specification does not accept a path.  Enter just the filename, such as SITEMAP.HTM.


The Database <database> does not exist.
The Database <database> does not exist. Please select another.

This error has the following cause and solution:

•	You are trying to find a database that does not exist.

Choose the Browse button to look for the correct Visual SourceSafe database, or No to cancel the operation.


SourceSafe cannot find a default database.
SourceSafe cannot find a default database. Would you like to select one?

This error has the following cause and solution:

•	Visual SourceSafe is trying to find a default database that does not exist.

Choose Yes to browse for the correct Visual SourceSafe database, or No to cancel the operation.


Could not login to <database>.
Could not login to <ftp site>.

This error has the following cause and solution:

•	You cannot log in to the specified ftp site.

You may be using an invalid address, invalid username, invalid password, or perhaps the site is just not responding.  Make sure you have the right ftp address. You can enter the ftp address using a web browser and see if the address is valid.


Could not Deploy <project> to <host>.

This error has the following cause and solution:

•	Visual SourceSafe was unable to open a connection to the specified FTP host and deploy your project.

Check your network connections, and check to be sure you entered the correct syntax for your FTP host.  This error could also be caused if your FTP host is not available at this time.

This message can also mean that you are out of disk space.  It could also mean that you don't have permission to write to the location although you may have read permission.


The URL for project %s was not set properly.

This error has the following cause and solution:

•	You set a bad URL path for a web project, or the URL uses a syntax that Visual SourceSafe does not understand (for instance, it might use www.microsoft.com/... instead of http://www.microsoft.com/...)

Use the Administrator program to set a proper URL.


An error occurred while checking hyperlinks for <file>.

This error has the following cause and solution:

•	The working folder path, Visual SourceSafe specification, or URL was too long..

Check that you aren't exceeding path limits for folder, specification, or URL.  Check that htmlfilt.dll is still present on your system and registered properly (re-running the client installation should fix this problem).


A link in <file> was ignored because it was too long.

This error has the following cause and solution:

•	The URL is too long for the internal buffer.

Use a shorter URL.


No HTML files were available in this project to check hyperlinks.

This error has the following cause and solution:

•	This informational message tells you that no files were checked for web hyperlinks because no HTML files were found.

If you expected HTML files in this project, check that they were added properly and that you entered the correct project name..


The base URL for this web project, '<project>', has bad URL syntax.

This error has the following cause and solution:

•	The URL that you entered for the base URL for a Visual SourceSafe web project has bad URL syntax.

Valid syntax for the URL is shown in these examples:

http://www.microsoft.com/default.htm

http://www.microsoft.com

You can change the URL in the Web Projects tab of the Visual SourceSafe Administrator Tools options dialog box, or edit the URL in the SRCSAFE.INI file.


# Unable to load the HTML parser.
Unable to load the HTML parser.

This error has the following cause and solution:

•	You have a corrupted Visual SourceSafe installation. Either the DLL is gone or the registry isn't set to the right DLL.

Re-install Visual SourceSafe.


This command requires internet components which are not installed on your machine.

This error has the following cause and solution:

•	You tried to use the  Check Web Links command on a RISC platform, but there wasn't a WININET.DLL to distribute when we shipped Visual SourceSafe.  You can get this required DLL when a RISC version of the browser exists, or

•	You are missing the correct version of WININET.DLL on your Intel or Alpha computer.  Check to see if the file has been moved or renamed.

To make sure you have the latest internet components, go to http://www.microsoft.com/ie/ and download Microsoft Internet Explorer 3.0 or higher.  Then restart Visual SourceSafe to enable this command.


Could not display this URL.

This error has the following cause and solution:

•	You tried to check an external web link, but there was no web browser we could find in the register to handle a http:: path; or, the link syntax was incorrect for ShellExecute (this could happen if you tried to check a virtual root by double clicking on it instead of setting the virtual root).

Install Internet Explorer 3.0 (or later).


Warning: the Rollback command will branch this file, breaking its link to other projects that share it.

This warning has the following cause and solution:

•	This warning occurs when you roll back a file that has been branched or is pinned in another project.

Choose Yes to continue, or No to cancel.


Get on Checked Out File Dialog

This message has the following cause and solution:

•	You chose to get a file when it was already checked out.

When you get a file, a new copy is written to your working folder.  If you already have the file checked out, you may have made changes that will be overwritten.  In this situation, Visual SourceSafe gives you some options:

•	Choose replace to overwrite the working folder file.

•	Choose Merge to merge changes from the working folder file into the Visual SourceSafe database file.

•	Choose Leave to leave the working folder file alone (the Get command will be ignored for that file).

•	Choose Cancel to cancel the get operation.

•	Choose Apply to all items to have your choices in this dialog apply to all other files you currently have checked out.


The Admin user currently has no SourceSafe password.

This message has the following cause and solution:

•	You have not assigned a password for the administrator user of the Administrator program.

Assign a password to the Admin user by choosing the Users Change Password command.  If you don't do this, any user can log in as Administrator and make changes to your Visual SourceSafe database.


You are about to remove the Admin user's SourceSafe password, which will allow any user to run the Administrator's program.

This message has the following cause and solution:

•	You are deleting the Admin user's password.

Leaving the Admin user with no password is a security risk, because then any user can log into the Administrator program and make changes to your Visual SourceSafe database. Are you sure you want to remove the Admin user's SourceSafe password?  Choose Yes to continue, or No to cancel the operation.


The URL <URL> does not have proper HTTP URL syntax.

This message has the following cause and solution:

•	The URL that you entered has bad URL syntax.

Valid syntax for the URL is shown in these examples:

http://www.microsoft.com/default.htm

http://www.microsoft.com


The deploy path <path> is not a proper file system or FTP deploy path.

This message has the following cause and solution:

•	One of the paths entered for deploying the project is either not a proper operating system file system path or is not a proper FTP URL.

ftp paths can look like one of the following.

ftp://user:user@www.microsoft.com/ssafe

ftp://user@www.microsoft.com/ssafe

ftp://www.microsoft.com/ssafe

They always start with “ftp://”.  They always end with the ftp address (server name and, optionally, directory path).  In between, you may have nothing (as in the bottom example above).  Or, you may have a username (as in the middle), or a username and password (as on the top).


Please enter a number between 0 and 32767.

This message has the following cause and solution:

•	You have not entered a number of context lines between 0 and 32767.

Context lines are the lines immediately preceding and following a difference.  Showing these lines  in a difference display helps you understand the context of the change or difference.  If you have checked the Show Context box in the Advanced options of the Show Difference command, you need to specify the number of preceding and following lines to show.