The Microsoft KnowledgeBase Archive

Visual SourceSafe

• Q163056: ACC97: Access IPF Using Find on Object That Is Checked In
• Q162851: ACC97: "Couldn't find object" Error Checking Out Table/Query
• Q162825: ACC97: Customizing Command Bar Does Not Prompt for Check-Out
• Q164238: ACC97: Duplicate Relationships Multiply in Back-End Database
• Q163278: ACC97: Err Checking Out Data Object with Linked Exchange Table
• Q162929: ACC97: Err Msg: "Could not create a valid file name" in VSS
• Q169279: ACC97: Error in Documenter If Object Can't Be Checked Out
• Q163705: ACC97: Error "Invalid DOS 8.3 Name" Adding DB to SourceSafe
• Q163345: ACC97: Error Running Switchboard Manager in SourceSafe Database
• Q163349: ACC97: IPF Adding DB with Large Number of Objects to VSS 4.0
• Q167847: ACC97: IPF Executing VSS Add and Create Commands at Same Time
• Q163346: ACC97: Linked Table Manager Doesn't Prompt You to Check Out Data
• Q169278: ACC97: MS Access Hangs Adding DB to VSS While in Break Mode
• Q163343: ACC97: No SourceSafe Symbols in Large Icon View
• Q163509: ACC97: Object Description Property Not Saved in SourceSafe
• Q170984: ACC97: Results Dialog Box Remains After First Check Out
• Q163704: ACC97: Some Access Commands Don't Prompt to Check Out VSS Module
• Q162823: ACC97: SourceSafe Integration Alerts Do Not Use Office Assistant
• Q167592: ACC97: SourceSafe Integration Tips
• Q163348: ACC97: Tables That Appear to Be Checked In in VSS Are Not
• Q162933: ACC97: User Without Permissions Can Check Out an Object in VSS
• Q171350: BUG: Analyze Always Updates aaaaaaaa.cnt
• Q181717: BUG: Analyze Problems with Open Log Files
• Q176551: BUG: Automation Events Not Received by VBasic Applications
• Q131955: BUG: Cannot Set Project Level Rights with SourceSafe's SSADMIN
• Q156878: BUG: Checking Out .VBP Overwrites Unsaved Changes in Project
• Q141209: BUG: Delete User Help Error: "No Additional Help Is Available"
• Q161578: BUG: Duplicate Entries Appear in Open Database Dialog Box
• Q138345: BUG: Error "File <filename> Not Found" When Adding Files
• Q156872: BUG: Errors Checking In or Out a Custom Resource File (.RES)
• Q177409: BUG: "Failed to Reload Project" Error When Checking In VB File
• Q149678: BUG: File Dates Do Not Change After a Rollback
• Q166261: BUG: "File is Exclusively Checked Out" Error
• Q155889: BUG: File Loses One Byte When Checked Out
• Q153503: BUG: Fonts are Corrupt or Extremely Large in Windows 95
• Q157716: BUG: Invalid Handle Message When Attempting a Show Diffs
• Q159777: BUG: Invalid Syntax Error When Logging On to Visual SourceSafe
• Q129192: BUG: Keyword Expansion Fails on the Macintosh
• Q168247: BUG: Keywords Cause New Version When "Undo Check Out" Set
• Q142580: BUGLIST: List of Problems in Visual SourceSafe 4.0
• Q154470: BUG: Long File Name Working Directory Not Created
• Q154835: BUG: "Project History Options" Won't Search for Labels in File
• Q140362: BUG: PVCS_SS Does Not Work with PVCS for Windows NT
• Q176351: BUG: Referenced Project Causes "Failed to Reload the Project"
• Q142092: BUG: Report to File "Access to File Denied" Error Message
• Q130145: BUG: SourceSafe and Windows Debug Kernel Causes Termination
• Q148892: BUG: SourceSafe File Not Found Error When VB Deletes .FRX File
• Q129191: BUG: SourceSafe for MS-DOS Hangs on Visual Difference
• Q176353: BUG: SourceSafe OLE Automation Does Not Support Label Comments
• Q130270: BUG: SourceSafe Reports a Date/Time of 1/1/70
• Q129189: BUG: SourceSafe Suddenly Terminates After Running a Long Time
• Q128238: BUG: SourceSafe Update Command Fails on Large Binary File
• Q178398: BUG: SssccSP2.exe: "The Database is Unavailable..." When Opening
• Q138480: BUG: Using the Keyboard in SourceSafe Administrator May Fail
• Q141058: BUG: Visual Basic .FRX File Not Added to SourceSafe
• Q149002: BUG: Visual Basic Project Window Not Displaying Project Files
• Q149788: BUG: Visual SourceSafe Books Online Isn't Properly Installed
• Q141547: BUG: Visual SourceSafe Help System Searches for Wrong HLP File
• Q176352: BUG: VSSItem Does Not Handle Strings Greater Than 128 Bytes
• Q142959: BUG: YMD Date Format Causes Improper History Selection
• Q148812: Configuring Visual SourceSafe Explorer to Use the System Font
• Q148511: Default Content of the Srcsafe.ini File
• Q158431: Deploying a Project Adds Two .GIF Files
• Q159774: DOCERR: Adding Visual C++ Projects to Source Control
• Q127189: DOCERR: Additional SourceSafe INI Settings
• Q132972: DOCERR: Corrections for Errors in SourceSafe 3.1 Documentation
• Q131023: DOC: How to Set Up a Shadow Directory
• Q142157: DOC: Merge Branches Option Doesn't Work at Project Level
• Q147906: DOC: Rights.bak File Is Not Necessarily Present
• Q127188: DOC: SourceSafe Undocumented Command Line Switches
• Q165417: DOC: Toolbar_Size Not Implemented in VSS 5
• Q153508: DOC: User's Guide Gives Wrong Required Windows NT Version
• Q140317: DOC: Visual SourceSafe Treats Binary Files Differently
• Q135332: FAQ: Visual SourceSafe Installation and Setup Issues
• Q135995: FAQ: Visual SourceSafe Integration with Visual Basic 4.0
• Q136019: FAQ: Visual SourceSafe Integration with Visual C++ 4.0
• Q165883: FILE: Errors with Large Recursive Branch and Share Operations
• Q131895: FILE: SourceSafe Knowledge Base As Help File (June 1995)
• Q176780: FILE: Use Guidscan.exe to View or Change GUID in a VSS Database
• Q164152: FILE: VC Hangs When Clicking Advanced Button on Source Control
• Q127061: FIX: Add File Dialog Forces Uppercase Filename
• Q156454: FIX: Adding File Causes Error if Name Contains a Space
• Q165776: FIX: Admin Cannot See Files with Project Security Enabled
• Q139299: FIX: Ampersand (&) Appears as Underscore (_) in the Explorer
• Q171535: FIX: ANALYZE Crashes When No Log Entries Found in Log File
• Q167274: FIX: Analyze May Hang When Running on Large Databases
• Q174875: FIX: Bogus "File is exclusively checked out" Error
• Q174874: FIX: Branched Files Restored to New Database Cause Corruption
• Q157813: FIX: Branch or Rollback of Shared File May Cause Corruption
• Q151703: FIX: Cannot Print a SourceSafe Report From Windows 95
• Q140319: FIX: Can't Save 'Assume Proj Based on Working Dir' Setting
• Q140361: FIX: Comment_Template Setting Doesn't Work in Srcsafe.ini File
• Q156451: FIX: DDCONV Causes GP Fault During Database Conversion
• Q167737: FIX: Deploy to a Unix Server Via FTP Fails
• Q132931: FIX: Drag/Drop Executes Create and Add with Insufficient Rights
• Q150961: FIX: Error Accessing Source Code Control System
• Q129193: FIX: File Added with No Extension is Handled Incorrectly
• Q162533: FIX: "File or Project Not Found" Errors Between Mac & PC Clients
• Q131446: FIX: File or Project Not Found If Add or Rename Long Filename
• Q172096: FIX: Forms Under Source Control Open Slowly
• Q153871: FIX: How to Install When Setup Fails on Novell
• Q174879: FIX: Incorrect Syntax on Keywords May Delete Text
• Q139672: FIX: Initialization Var Shadow_SetTime Set to Invalid Value
• Q174876: FIX: "Invalid DOS Path" to SSADMIN.INI on Unix
• Q174878: FIX: Large Buttons When Resetting Toolbar
• Q142509: FIX: List of Problems Solved by Visual SourceSafe 4.0
• Q174873: FIX: Lost Net Connection Causes Source Code Control to Hang
• Q166469: FIX: Multiple Check In Fails with Keyword Expansion
• Q142463: FIX: Non-SourceSafe Visual Test Files Show Up as Checked Out
• Q151002: FIX: No Response to Natural Keyboard Right-Mouse Button
• Q151004: FIX: "PRG" File Type Missing in FoxPro File Group
• Q151000: FIX: Problems with the Task Bar in Windows 95
• Q157082: FIX: Rollback of a Shared File Rolls to Unexpected Version
• Q174877: FIX: Selecting a File in SourceSafe Explorer Causes Refresh
• Q155783: FIX: Share Dialog Box Appears Unexpectedly
• Q171534: FIX: Source Code Control Integration Holds .dat Files Open
• Q141398: FIX: "Source Control" Does Not Appear in Tools Menu w/ MIPS
• Q129190: FIX: SourceSafe Command Line Fails to Create Output File
• Q130140: FIX: SourceSafe Might Not Get Long Filenames on Windows NT
• Q172337: FIX: SSARC & SSRESTOR Do Not Store Macintosh Resource Fork Data
• Q131445: FIX: "Timeout Locking File: UM" Error Occurs at Startup
• Q142464: FIX: "Too Many File Handles" in VB Enterprise SourceSafe
• Q159776: FIX: VC++ Crash When Adding Test Case Under Source-Code Control
• Q154469: FIX: Visual SourceSafe 4.0 Increases Processor Usage
• Q141016: FIX: Visual SourceSafe Books Online Help Is for Visual Basic
• Q139729: FIX: Visual SourceSafe Can't Associate File That Has 2 Periods
• Q140363: FIX: Visual SourceSafe Slows as It Increases Processor Usage
• Q158430: FIX: VSS 4.x Integration with VC 4.x under Windows NT 4.0
• Q167273: FIX: VSS Editor/Viewer Removes and Replaces Characters
• Q164585: FIX: VSS Log Files Not Deleted Correctly on NetWare
• Q131094: Gray State Check Boxes in SourceSafe
• Q157714: How SourceSafe Stores Log Files
• Q157984: How SourceSafe Uses the DATA Directory
• Q124529: HOWTO: Access SourceSafe Code From a Central Directory
• Q141501: How to Add SourceSafe for Unix to SourceSafe for Windows
• Q150064: How to Branch to a Specific Version of a Project
• Q123471: HOWTO: Change the Data Directory Location
• Q140537: HOWTO: Change the Data Directory Location for Integration Apps
• Q175950: HOWTO: Change the Name of a Visual SourceSafe Database
• Q162300: HOWTO: Converting VFP3 Source Control Projects to VFP5
• Q123467: How to Create a New Database in SourceSafe
• Q123472: HOWTO: Create a Unique SRCSAFE.INI File
• Q154968: HOWTO: Customizing the Differences Window
• Q158702: HOWTO: Details About How ANALYZE Passes Work
• Q133054: HOWTO: Detect and Fix Database Corruption Errors in SSafe
• Q180945: HOWTO: Disconnect a Project from Source Control
• Q171116: HOWTO: Enable VSS Integration with FrontPage and Visual InterDev
• Q167290: HOWTO: Enabling SourceSafe Locking
• Q158475: HOWTO: Find Missing Versions in the Project History Dialog Box
• Q169927: HOWTO: Get History Using SourceSafe OLE Automation in C++
• Q139298: HOWTO: Include Specific File Revisions in a Project Label
• Q123473: HOWTO: Increase Performance in SourceSafe
• Q129112: How to Install SourceSafe on a Windows 95 Workstation
• Q130141: HOWTO: Install SourceSafe on a Windows Client Workstation
• Q130142: HOWTO: Install SourceSafe on a Windows NT Client Workstation.
• Q162114: How To Issue a Recursive GET Based on a Project Label
• Q140320: How To List the Current Version of All Files in a Project
• Q168833: HOWTO: Load the Visual Basic Sample Projects into SourceSafe
• Q163797: HOWTO: Locking a SourceSafe Database
• Q123474: How To Logon With a Name Other than the System Logon
• Q141504: HOWTO: Make SourceSafe Keyword Expansion Work in Text Docs
• Q176909: HOWTO: Move a VSS Database or Project to New Location
• Q136021: HOWTO: Move or Rename Files Used with Visual C++
• Q169260: HOWTO: No Command Line Equivalent for Some Web Features
• Q169928: HOWTO: Open a SourceSafe Database with OLE Automation in C++
• Q167134: HOWTO: Opening SourceSafe to a Specific Project
• Q176350: HOWTO: Open Visual SourceSafe to a Specific Database
• Q151705: HOWTO: Perform a Recursive Check-in at the Command Line
• Q153493: HOWTO: Perform a RollBack Without Losing History
• Q166305: HOWTO: Reconnecting a Visual C++ Project to Source Control
• Q153500: HOWTO: Recover Disk Space in Visual SourceSafe
• Q128723: HOWTO: Reference a Time on the Command Line
• Q126786: HOWTO: Remove or Change a Label
• Q132930: HOWTO: Run Ddconv in Visual SourceSafe
• Q131956: HOWTO: Run the Macintosh SourceSafe SSADMIN Tool
• Q133377: HOWTO: Search for SourceSafe Articles Using KBKeywords
• Q157401: How To Set a Working Directory
• Q156512: How To Set the Working Directory in SourceSafe Macintosh
• Q138344: How To Set up a Shadow Dir in Visual SourceSafe Administrator
• Q138475: How To Set Up Multiple Check Outs on a Project Basis
• Q127104: HOWTO: Set Up Multiple SourceSafe Databases
• Q157636: HOWTO: Set Up Source Code Control with SourceSafe
• Q128636: HOWTO: Set Up SourceSafe for Replication Under Windows NT
• Q132703: HOWTO: Set Up SourceSafe for the Macintosh Manually
• Q155678: HOWTO: Share Files Under Source-Code Control in Visual C++
• Q131453: HOWTO: Tips for Using Visual Basic 3.0 with SourceSafe
• Q175758: HOWTO: Trapping Visual SourceSafe OLE errors
• Q131449: HOWTO: Troubleshoot "Out of Memory" Errors
• Q153873: HOWTO: Upgrade from SourceSafe 3.x to Visual SourceSafe 4.0
• Q131451: How to Upgrade SourceSafe Manually
• Q154081: HOWTO: Use a Template for Comments When Checking In Files
• Q136020: HOWTO: Use Glyphs in Visual C++ 4.0 with Source Code Control
• Q161577: HOWTO: Use Keyword Expansion in HTML Files
• Q131447: HOWTO: Use PHYSICAL Command to Find SourceSafe Database File
• Q148513: HOWTO: Use Pin and Label for Quality Assurance
• Q158219: How To Use SourceSafe Over a RAS or ISDN Connection
• Q150642: How To Use SSINT.EXE in Visual SourceSafe
• Q138147: HOWTO: Use the SourceSafe Explorer to Modify the Ss.ini File
• Q124526: HOWTO: Use the Windows Command Line
• Q159270: How Visual SourceSafe's Merge Process Works
• Q169257: INFO: Actions That Perform an Implicit GET
• Q140316: INFO: All Variable Settings for Visual SourceSafe .INI File
• Q135643: INFO:Basic Troubleshooting Converting from Delta to SourceSafe
• Q132921: INFO: Branching or Separating SourceSafe Files and Projects
• Q169535: INFO: Cannot Set EOL Option from the Visual SourceSafe 5.0 GUI
• Q136400: INFO: Changing Visual SourceSafe User Name in Visual Basic
• Q164941: INFO: Command Line Equivalent of "Build Tree" Option
• Q175760: INFO: Contents of Analyze Window Limited to ~30,000 Characters
• Q176553: INFO: Database Architecture Changes in 4.0, 4.0a, and 5.0
• Q153872: INFO: DDConv Messages of Visual SourceSafe 4.0
• Q131450: INFO: Description of Files in the \SS\DATA Directory
• Q148512: INFO:Description of the Properties/About Command Line Commands
• Q181089: INFO: Dialog Box Appears Even When No Conflicts Exist
• Q170750: INFO: End of Line Character Settings for SourceSafe
• Q152807: INFO: Error Messages from Analyze Tool of Visual SourceSafe
• Q168635: INFO: Explanation of Diff_Ignore
• Q124525: INFO: How SourceSafe Locks Files in the DATA Directory
• Q123470: INFO: How SourceSafe Selects a Viewer for a File
• Q151975: INFO:List of SourceSafe Error Messages Documented in KB on Web
• Q163843: INFO: Managing Linked Tables When You Create a New DB from VSS
• Q132971: INFO: Merging SourceSafe Files
• Q150645: INFO: Minor Inconsistencies in the Header Log for <filename>
• Q138342: INFO: New Files in Visual SourceSafe Version 4.0
• Q157527: INFO: New Visual SourceSafe Commands and Functionality
• Q139358: INFO: Readme.wri: Section 1, Software Installation Information
• Q139359: INFO: Readme.wri: Section 2, General Notes and Tips
• Q139361: INFO: Readme.wri: Section 3, Issues and Considerations
• Q139360: INFO: Readme.wri: Section 4, Documentation Notes
• Q139362: INFO: Readme.wri: Section 5, New Features of Visual SourceSafe
• Q131022: INFO: Required Network Rights for the SourceSafe Directories
• Q138479: INFO: Required Rights for SourceSafe Commands
• Q131772: INFO: Setting Compare to Checksum Speeds GET Command
• Q131773: INFO: Setting Compare to Time Increases Speed of GET Command
• Q132922: INFO: Sharing SourceSafe Files
• Q132923: INFO: Sharing SourceSafe Projects
• Q151702: INFO: SourceSafe Database Use of Disk Space on FAT Partition
• Q132892: INFO: SourceSafe May Modify Some Files
• Q124530: INFO: SourceSafe - Project Oriented Version Control
• Q123475: INFO: SourceSafe System Capacities and Specifications
• Q158218: INFO: Support Options for Visual SourceSafe
• Q132891: INFO: The Meaning of v.# for User Name in SourceSafe
• Q147585: INFO: The Mssccprj.scc File and How Is It Used
• Q176875: INFO: The Primary Functions of Ssarc.exe and Ssrestor.exe
• Q136325: INFO: Three Types of Drag-and-Drop with Visual SourceSafe
• Q136399: INFO: Visual Basic and Source Code Control Glyphs
• Q150293: INFO: Visual Basic & Visual SourceSafe Add-In Options
• Q138736: INFO: Visual C++ Programmers Guide to Visual SourceSafe
• Q124527: INFO: Visual Difference and Viewer Window Search
• Q166259: INFO: Visual Interdev/Visual SourceSafe Integration Discussion
• Q139891: INFO: Visual SourceSafe Installation is Processor Specific
• Q133018: INFO: Visual SourceSafe Setup Registration Settings
• Q133101: INFO: Visual SourceSafe Setup Uses ACME 95
• Q157720: INFO: VSS 5.0 Readme: Sec. 1, Software Installation Information
• Q157717: INFO: VSS 5.0 Readme: Sec. 2, General Notes and Tips
• Q157718: INFO: VSS 5.0 Readme: Sec. 3, New Features in Visual SourceSafe
• Q157719: INFO: VSS 5.0 Readme: Sec. 4 & 5, Users of VSS 4.0/VSS Home Page
• Q165496: INFO: VSS Integration With MS Word and MS Excel
• Q149586: INFO: VSS on Windows NT Workstation w/ FAT Partition
• Q170749: INFO: What the Window Position Values in Some INI Variables Mean
• Q168634: INFO: When -d Switch of Analyze Deletes Files
• Q156513: INFO: Which Visual C++ Files to Add to Source-Code Control
• Q138299: Legal Visual SourceSafe Naming Conventions
• Q155631: Message "Error Writing to File" Occurs When Checking In a File
• Q134369: Microsoft SourceSafe Frequently Asked Questions (FAQ)
• Q138343: New Features of Ddconv.exe in Visual SourceSafe Version 4.0
• Q140253: Obsolete .INI File Variables in Visual SourceSafe
• Q123466: PATCH: FIXFRE.EXE Fixes Database Errors Reported by ANALYZE.EXE
• Q123427: PATCH: Use FIXPROJ.EXE to Fix Project Errors in SourceSafe
• Q157983: Platform Considerations with OLE Automation
• Q141548: PRB: 16-Bit Visual Basic Requires 16-Bit SourceSafe
• Q155971: PRB: 32-bit SSEXP.EXE Doesn't Work but 16-bit SSEXP.EXE Does
• Q154486: PRB: Access Denied or File Locked When Log In to SourceSafe
• Q155391: PRB: ACME Setup Problems During 16-bit Installation of VSS 4.0
• Q150419: PRB: "Add Files to SourceSafe" Add-in Menu Item is Disabled
• Q167258: PRB: Analyze Leaves Files with .old Extension in Database
• Q165831: PRB: Anonymous User in NT Admin Group Breaks Source Control
• Q155888: PRB: Binary Files with Keyword Expansion Corrupted
• Q133017: PRB: Branching Files in SourceSafe Causes Lost Disk Space
• Q159278: PRB: Can Log on to a Locked Visual SourceSafe Database
• Q181719: PRB: "Cannot Access the ClassView Information File..."
• Q161576: PRB: Cannot Checkout a File When Multiple Checkouts are Enabled
• Q154400: PRB: Can't Map File to the Project '$' Message in Dev Studio
• Q142156: PRB: Can't See Objects on Back Tabs If Using VB SSTAB Control
• Q153506: PRB: Can't Set Working Directory by Using .ini File
• Q154834: PRB: Checking Out Forms and MAK File Loses Changes in Memory
• Q141353: PRB: Check-in That Uses Drag and Drop Causes Application Error
• Q140252: PRB: ClassWizard Disables Add Function & Add Variable Buttons
• Q145744: PRB: Client Installed from ReadOnly Server Won't Start
• Q158160: PRB: Cloaked Projects are Deployed
• Q127993: PRB: Corrupt Binary File After Merging with SourceSafe
• Q136401: PRB: Data Path Errors Starting SourceSafe
• Q172376: PRB:Ddcerr.log Only Reports "DDCONV initializing" During Upgrade
• Q132929: PRB: "DDE Connection Failed" When Viewing a File
• Q135644: PRB: Deleted Project Files Are Not Converted with DELTA_SS.EXE
• Q129186: PRB: Delta Labels Are Not Converted with DELTA_SS.EXE
• Q155438: PRB: "Directory Not Found" When Using Macintosh Client 4.00a
• Q172157: PRB: Do Not Use SourceSafe When Running SSARC or SSRESTO
• Q155394: PRB: Double Quotes in DIR Path in INI File Can Result in Crash
• Q167774: PRB: Enabling VSS4.x Integration with VB5 Must be Done Manually
• Q140593: PRB: Error "Names.dat may be corrupt" Appears
• Q151006: PRB: Error: Physical File Parent Project <proj name> Not Found
• Q153501: PRB: "Error reading from file" When Logging into SourceSafe
• Q181718: PRB: "Error Updating the SourceSafe Database via DDCONVW.EXE"
• Q158701: PRB: Error When Renaming a File That Is Checked Out
• Q155754: PRB: File Could Not Be Mapped to the SourceSafe Project
• Q167263: PRB: <filename> is Already Open
• Q147837: PRB: "File not Found" Error Message During Checkin
• Q149378: PRB: File Not Found Error When You Add New Users
• Q158471: PRB: 'File not found' When Attempting Command Line Check In
• Q164684: PRB: "File or Project not Found" Adding Files via Integration
• Q155584: PRB: Files Missing or Not Displayed in GUI Interface
• Q129187: PRB: Files Truncated One Byte When Placed in SourceSafe
• Q171346: PRB: Filter String Exceeds the Maximum Length of 511
• Q159775: PRB: General Protection Fault Occurs On VSS Launch
• Q166896: PRB: Header Files in External Dep Folder Aren't Added to SCC
• Q146017: PRB: History in Explorer Differs from History File w/ Keywords
• Q124528: PRB: How to Handle the Error "INI in 2.2 format"
• Q123469: PRB: How to Handle the "invalid serial number" Error
• Q123468: PRB: "incompatible database" Error
• Q150646: PRB: "Incompatible Database Version" Error Running Analyze
• Q154294: PRB: Inconsistent Use of Shadow Directory Checkin Terminology
• Q136286: PRB: Installation Conflict w/C Run-Time Library (MSVCRT20.DLL)
• Q155437: PRB: "Invalid DOS Path" Error Message
• Q162530: PRB: Invalid Handle on Client When Journal_Text Set to Bad Path
• Q131092: PRB: Keyword Expansion Is Case Sensitive
• Q131452: PRB: Links to Separated Files Not Restored on Rollback
• Q140594: PRB: Local SSADMIN Writes to Local (Not Server) Srcsafe.ini
• Q132421: PRB: Lock_Mode = lockfile Causes "Timeout Locking File" Error
• Q173405: PRB: Misleading Message When Checking Out Older File Version
• Q135720: PRB: Moving Project in SourceSafe Explorer Causes Error in VB
• Q166260: PRB: No Workspace or Project Files Found in Selected SCC Project
• Q155976: PRB: Output from SourceSafe Command Lines may be Truncated
• Q142763: PRB: Path Problems on Client Installation of SourceSafe
• Q159690: PRB: Problem Adding Objects Created in VBA to SourceSafe
• Q155055: PRB: Problem Adding VB File from Other Drive to VSS Project
• Q173065: PRB: Problems After Branching Integrated DevStudio Projects
• Q163347: PRB: Project Created but No Objects If Add to VSS Is Canceled
• Q162113: PRB: Project Modification Not Reflected in Shadow Directory
• Q129188: PRB: PVCS Labels Are Not Converted with PVCS_SS.EXE
• Q157533: PRB: PVCS to SourceSafe Conversion Fails
• Q176732: PRB: Read-Only Files in Shadow Folder Are Not Updated
• Q150417: PRB: Read-Only SSTab Does Not Display Child Controls Properly
• Q176878: PRB: Replacing Names.dat File Changes Long File Names
• Q173387: PRB: Restoring an Archive of an Entire Database
• Q154829: PRB: Rights by Project Are Not Always Inherited
• Q156717: PRB: Rollback of Shared File Forces a Branch
• Q161727: PRB: SCC API Error "Project Created" Occurs When Opening a PJX
• Q162232: PRB: Server Error: Visual Source Safe Failure
• Q150643: PRB: Setting Wrong System Date Causes Lost Project History
• Q172158: PRB: Setup error: "You must have NT administrative privileges"
• Q153511: PRB: Shared Project, Branch Menu Option Is Not Available
• Q131093: PRB: SourceSafe 3.1 Cannot Use UNC Names
• Q130272: PRB: SourceSafe Appears to Use the Incorrect Date/Time
• Q130271: PRB: SourceSafe Can No Longer Detect Novell User Names
• Q162931: PRB: SourceSafe Commands not available for RunCommand method
• Q134834: PRB: SourceSafe Fails with Norton Desktop Version 3.0
• Q130144: PRB: SourceSafe for Windows Setup Fails w/ Novell VLM.EXE 1.1
• Q162820: PRB: SourceSafe/MS Access Does Not Allow Project Sharing
• Q154279: PRB: SourceSafe Status Truncates Filenames to 20 Characters
• Q123476: PRB:SoureSafe "Error locking file" on Windows NT or Multi-User
• Q161610: PRB: SSARC/SSRESTOR Change 4.0 Database to 4.0a/5.0 Format
• Q135357: PRB: Sync Between Visual SourceSafe and VB Is Delayed
• Q160914: PRB: The Data File for <file> (<physical file>) Was Not Found
• Q143114: PRB: Trouble Installing Multiple Servers from Single Computer
• Q155390: PRB: Unable to Add Project Error in Visual Basic Integration
• Q138433: PRB: Unable to Open <path Name> When Running Analyze
• Q153502: PRB: Unable to Open Project Error When Running Analyze
• Q167262: PRB: Unable to Open User Login File
• Q168844: PRB: Undo Check Out Not Behaving As Expected
• Q174651: PRB: Unexpected Message: "Add this project to SourceSafe" in VB
• Q174650: PRB: VBG Files Do Not Appear to Work with Visual SourceSafe
• Q154828: PRB: Visual Basic Module Shuffle Looks Like Entire File Change
• Q139001: PRB: Visual C++ Integration Does Not Recognize .CLW Files
• Q147173: PRB: Visual C++ Seems to Hang - Updating Source Control Status
• Q136541: PRB: Visual SourceSafe Books Online Help Viewer Crashes
• Q135994: PRB: Visual SourceSafe Explorer Checks Out .FRM Without .FRX
• Q154080: PRB: Visual SourceSafe Journal File Not Updated
• Q155054: PRB: Visual SourceSafe Occasionally Saves .FRX File as Text
• Q160888: PRB: VSS Explorer Error: "This Is an Integration Only Project"
• Q162932: PRB: VSS Integration Dialog Box Does Not Respond to Keyboard
• Q157715: PRB: VSS OLE Add-in Model Not Supported by Visual Basic 4.0
• Q163438: PRB: Warning Message in MS Access After Installing ODE Tools
• Q158914: PRB: Web Root Busy Opening Source-Controlled Web
• Q165237: PRB: Word 97 Document Added to SourceSafe as Text File
• Q130176: Project versus File Labeling in SourceSafe
• Q150644: Quotes Required in Command Line for Names with Spaces
• Q150648: Resolving Files Checked Out by an Unavailable User
• Q139566: SAMPLE: Analyze5.Exe Utility for Visual SourceSafe
• Q130178: SAMPLE: FIXPRNT Fixes Database Errors Reported by ANALYZE.EXE
• Q151411: SAMPLE: New Version of Ssscc.dll Available
• Q151354: SAMPLE: Sslogin Utility to Validate User Name and Password
• Q150647: SAMPLE: Updated Visual SourceSafe 4.0 Ddconv.exe
• Q149382: Setting Options You Can Modify in the Srcsafe.ini File
• Q156448: Some Files and Projects are Upper Case after Upgrade
• Q155784: SourceSafe Alpha/MIPS Files Not on VB Enterprise CD-ROMs
• Q157985: SSARC.EXE Can Be Run by Anyone if No Admin Password
• Q158469: Time Difference in Checking Out vs. Getting File in SourceSafe
• Q157982: Understanding Promotions
• Q138296: Using UNC Paths in Visual SourceSafe
• Q137017: Visual Basic 4.0 File Types & Version Control Recommendations
• Q138148: Visual SourceSafe Directory Listing
• Q138385: Visual SourceSafe Shortcut Keys
• Q138298: Visual SourceSafe System Capacities and Specifications
• Q138387: Visual SourceSafe Viewer Accelerator Keys

Powered by helparchive