-
Title
How to set up Toad and legacy source control without Team Coding. -
Description
How to set up Toad and legacy source control without Team Coding.
-
Resolution
The steps can still be found in Toad's help menu, although Toad is moving away from legacy source control to more integration with Team Coding.
1. Go into Toad's View | Toad Options.
2. Click on Team Coding. Check the settings for legacy source control.
3. Set the Source Control Provider to your legacy source control.
Basic Source Control
Toad supports the Source Code Control (SCC), a Microsoft API. It defines a standard interface between development environments and source control products. The SCC API provides functions to perform the common source control operations such as check-out, check-in, and add file.
SCC is implemented in:
Schema Browser | Favorites page
Project Manager
Editor
Script Debugger
If you need more functionality than basic check-in and check-out functions, please consider using the Team Coding. Team Coding and SCC are not mutually exclusive. Please see Team Coding and SCC Interaction for more information.
The following vendors support SCC API and have been tested with Toad:
Microsoft Visual SourceSafe 6.0 on Win98 and NT4/Win2K/XP
PVCS 6.6.0, 6.7.0, 6.8.0, 6.8.1, 7.5.0 (requires the VM Development Interface) on NT4/Win2K/XP
StarTeam 5.2(requires the VB and Developer Studio Integration option) on Win98 and NT4/Win2K/XP
Quma QVCS 3.5 (use the QVCS client to add QVCS as a Source Control Provider)
CS-RCS 2.5.140 and 3.0.192 (ComponentSoftware) on NT4/Win2K/XP
CVS 1.11.14
Note: Earlier versions of these software products have not been tested with Toad and we cannot guarantee their compatibility. Other vendors may conform to the API, but have not been tested with Toad; therefore, integration cannot be guaranteed at this time.
Each SCC compliant product will create an entry in the registry identifying it as an SCC provider and identifying the location of the DLL used to call the SCC functions.
Note: The client portion of the Source Control install must be run. You cannot run only the server piece of the Source Control install.
Setting up Source Control for the first time.
1. Install your client.
2. Confirm your client is configured to support SCC API. You confirm this by checking that the client or the client install has created the SCC API registry key.
3. From the View menu, select Toad Options and click Source Control.
4. Select your SCC provider and check/uncheck options as desired. (See Source Control Options.)
5. Open your file in the Editor. Remember that Toad Source Control is run through the Editor.
6. Right-click in the Editor and choose Source Control. Click Select Project.
7. Your SCC provider will display a dialog box asking you to select a project. Depending on the provider and the configuration, it may also ask you to log in or browse for a database. It may provide a place for you to set a working folder. Refer to your Source Control provider's documentation for further details.
Note: The working directory for the selected project must match the directory where you loaded the file.
8. If the file is already stored in Source Control, you can check it in and out. Otherwise, you can right-click and select Source Control > Add File to add it to the Source Control database. This assigns it a checked-in status. You will have to check it out to modify it.
Source Control Options
You must also have the interface to the SCC configured by selecting the Source Control options in the View|Toad Options|Team Coding page.
To set the Source Control Options
From the drop-down menu, select the Source Control Provider that you want to use with Toad. The Source Control Provider drop-down lists the SCC providers found in the registry. If you do not have a Source Control Provider installed, the drop-down menu will be empty.
Note: If you switch providers, you should restart Toad.
Select or deselect the appropriate Prompt for Comment check boxes. Selected, a prompt for a comment will display with the respective action.