Article ID: 822845 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
When you try to add a Microsoft Access database project to Visual SourceSafe (VSS) by using the integration menus that Microsoft Office Developer adds, the database project is not added to VSS and you do not receive an error message.
This problem may occur after you upgrade from VSS 6.0c to VSS 6.0d. If you archive part of an existing database, and then restored it to a new blank database, the VSS command line and OLE Automation cannot retrieve older versions of any files in the database.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name -------------------------------------------------------- 13-Jun-2003 17:34 6.0.30613.0 225,280 Analyze.exe 13-Jun-2003 17:07 299,008 Ddconv.exe 13-Jun-2003 17:10 421,888 Ddupd.exe 13-Jun-2003 16:59 224,969 Delta_ss.exe 05-Jan-2002 12:48 7.0.9466.0 974,848 Mfc70.dll 13-Jun-2003 17:16 114,688 Mkss.exe 05-Jan-2002 11:37 7.0.9466.0 344,064 Msvcr70.dll 13-Jun-2003 16:59 231,143 Pvcs_ss.exe 27-Feb-1998 22:00 38,790 Readmess.htm 13-Jun-2003 17:03 397,312 Ss.exe 13-Jun-2003 17:36 6.0.30613.0 19,456 Ssadmin.exe 13-Jun-2003 17:05 6.0.30613.0 569,344 Ssapi.dll 13-Jun-2003 17:13 6.0.30613.0 532,480 Ssarc.exe 13-Jun-2003 17:35 6.0.30613.0 27,648 Ssexp.exe 13-Jun-2003 17:46 6.0.30613.0 1,220,608 Ssgui.dll 13-Jun-2003 17:46 6.0.30613.0 147,456 Ssint.exe 13-Jun-2003 17:17 155,648 Sslogin.exe 13-Jun-2003 17:15 6.0.30613.0 528,384 Ssrestor.exe 13-Jun-2003 17:43 6.0.30613.0 1,560,576 Ssscc.dll 13-Jun-2003 17:46 6.0.30613.0 499,712 Ssus.dll 13-Jun-2003 17:18 102,400 Testlock.exe 13-Jun-2003 17:19 147,456 Unlock.exe 13-Jun-2003 17:19 122,880 Updini.exe
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.