INFO: Visual Basic Programmer's Guide to Visual SourceSafe

 Last reviewed: June 3, 1997
Article ID: Q142823
The information in this article applies to:
  • Standard, Professional, and Enterprise Editions of Microsoft Visual Basic, 16-bit and 32-bit, for Windows, version 4.0
  • Microsoft Visual SourceSafe, version 4.0

SUMMARY

This article includes information that can be of use to anyone wishing to take advantage of the source code control features found in Microsoft Visual Basic version 4.0 for Windows, and specifically integration with Microsoft Visual SourceSafe, version 4.0. The following sections are covered:

  • Useful Microsoft Visual SourceSafe Knowledge Base articles
  • Visual SourceSafe and Electronic Information

This information is current for version 4.0 of Visual Basic and for version 4.0 of Visual SourceSafe. Previous versions of both Visual Basic and SourceSafe do not support integration.

MORE INFORMATION

Useful Visual SourceSafe Knowledge Base Articles

The following list includes articles that are useful in performing setup of Visual SourceSafe, verifying/utilizing integration of Visual SourceSafe with Visual Basic, and general usage of Visual SourceSafe. 

   Setup/Installation
   ------------------

   Q135332 -- FAQ: Visual SourceSafe Installation and Setup Issues
   Q135995 -- FAQ: Visual SourceSafe Integration w/Visual Basic 4.0
   Q133018 -- Visual SourceSafe Setup Registration Settings
   Q123468 -- How to Handle "Incompatible Database" Error
   Q136286 -- PRB: Possible Conflict w/MSVCRT20.DLL During Installation

   The README.WRI file that ships with Visual SourceSafe is also an
   excellent and timely source of installation information.

   Using Visual Basic with Visual SourceSafe
   -----------------------------------------

   Q133377 -- How to Search for SourceSafe Articles by KBSubcategory
   Q136399 -- Visual Basic and SourceCode Control Glyphs
   Q135720 -- PRB: Moving Project in SourceSafe Explorer Causes Error in VB
   Q136401 -- PRB: Visual SourceSafe "Invalid Data Path" Error
   Q137017 -- Visual Basic 4.0 File Types & Version Control Recommendations
   Q136400 -- Changing Visual SourceSafe User Name in Visual Basic
   Q135994 -- PRB: Visual SourceSafe Explorer Checks Out .FRM without .FRX
   Q135357 -- PRB: Sync Between Visual SourceSafe and VB Is Delayed

   General Usage
   -------------

   Q134369 -- Microsoft SourceSafe Frequently Asked Questions (FAQ)
   Q131895 -- SourceSafe Knowledge Base Available as Help File
   Q132922 -- Sharing SourceSafe Files
   Q132923 -- Sharing SourceSafe Projects
   Q132921 -- Branching or Separating SourceSafe Files and Projects
   Q132971 -- Merging SourceSafe Files
   Q133054 -- Detecting and Fixing Database Corruption Errors in SourceSafe

Visual SourceSafe and Electronic Information

The World Wide Web For Developer's Only Home Page offers useful information for all Microsoft developer products. Within it you can connect to home pages dedicated to either Visual Basic or Visual SourceSafe and connect to dedicated pages for the Knowledge Base. To access this home page, connect to: 

   http://www.microsoft.com/DevOnly
This web site contains rich content and award-winning services.
  • Microsoft Frequently Asked Questions
  • Microsoft Software Library
  • Microsoft Knowledge Base
  • Microsoft Wish
  • Microsoft Member BBSs (MSN only)

The Microsoft Support Desktop offers information from Microsoft Technical Support for all Microsoft products, including the full Knowledge Base. To access this information, connect to: 

   http://www.microsoft.com/Support

Additional query words: srcsafe ssafe
Keywords : IAPThird kbinterop kbusage ssint ssvb VB4ALL VB4WIN
Version : 4.0
Platform : NT WINDOWS
Issue type : kbinfo
Resolution Type : Info_Provided

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 3, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.