Microsoft Office 2000 Developer   

Using the Visual SourceSafe Add-In with the Visual Basic Environment

See Also

The new VBA Source Code Control add-in included with Microsoft Office 2000 Developer conveniently provides Visual SourceSafe functionality within the Office development environment.

Note   In order to use the VBA Source Code Control add-in, you must first load it into the Office environment. For information on loading the Office 2000 Developer add-ins, see Accessing Office 2000 Developer Tools.

How Source Code Control Works

While a group of Office developers work together to build a database application, the master copies of all the VBA objects are kept in a Visual SourceSafe project. Each developer works on a VBA project on their local workstation. Checking out source code objects from the Visual SourceSafe version control system copies them from the Visual SourceSafe project into the developer's project on the local workstation. Checking in source code objects copies them from the developer's local workstation into the Visual SourceSafe database.

For information about the types of items you can use with the VBA Source Code Control add-in, see Using Visual SourceSafe with Documents and VBA Code.

Visual SourceSafe provides useful versioning and control functionality. When you install the VBA Source Code Control add-in and place your project under source code control, the following commands are added to the VBA Source Code Control submenu on the Add-Ins menu.

These commands typically display a dialog box with a list box of all the objects in the Visual SourceSafe project that the command applies to. For instance, if you choose the Check In command, the list box is filled with all the objects that you currently have checked out. Select the items that apply for the chosen command, and then click OK. Depending on what you had selected before choosing the command, certain items in the list box may already be selected.