The author introduced the shortcomings of SourceSafe and hoped  to dissuade us from using SourceSafe, and have spared us the bad experiences he had.

Alan De Smet provided the missing features of the Micosoft SourceSafe:

• SourceSafe lacks usable branching support
• SourceSafe cannot be safely extended
• SourceSafe silently leaves stale files on your local system
• SourceSafe badly handles slow networks and the public internet
• Managing third party modules is difficult with SourceSafe
• Viewing and retrieving historical versions is extremely slow
• Difficult to maintain multiple local copies of one project

Alan De Smet also thought that the safety of SourceSafe was bad.

• SourceSafe degrades on large projects
• SourceSafe integration can crash Visual Studio
• SourceSafe relies on dangerous file sharing
• SourceSafe should be scanned for corruption weekly
• SourceSafe handles multiple time zones badly
• SourceSafe becomes corrupted

And at last, Alan De Smet  suggested us to transfer our souce control system to some better choice.

The original fulltext is here.  

• The Simplest way to change the row height of CListCtrl (0)
• Speed up loading of pages (1)
• Solution of fatal error RC1004: unexpected end of file found (11)
• Setup SCIM in Ubuntu 6.10 (0)
• Microsoft Visual C++ Tips (0)
• MessageBox support Ctrl+C to copy content (0)
• How to launch an Application with Admin privileges in VISTA (0)
• How to Get the Primary Domain name (0)
• CComModule in porting ATL DLL project to VC8 (0)
• 30 Great Tips of CListCtrl Program(2) (0)