Microsoft KB Archive/171840

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 16:36, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


FIX: Corrupt Project Error Opening One Project After Another

Article ID: 171840

Article Last Modified on 12/10/2003



APPLIES TO

  • Microsoft Visual Basic 5.0 Control Creation Edition
  • Microsoft Visual Basic 5.0 Learning Edition
  • Microsoft Visual Basic 5.0 Professional Edition
  • Microsoft Visual Basic 5.0 Enterprise Edition



This article was previously published under Q171840

SYMPTOMS

After loading one project file (.VBP) and proceeding to load a second project file, Visual Basic 5.0 reports that the second project is corrupted and cannot be loaded. However, the second project opens fine if opened by itself and no message about a corrupted project file appears.

CAUSE

In rare cases, Visual Basic incorrectly reads the project file, which causes this error.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been fixed in Visual Studio 97 Service Pack 2.

For more information on the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:

170365 INFO: Visual Studio 97 Service Packs - What, Where, and Why


For a list of the Visual Basic 5.0 bugs that were fixed in the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:

171554 INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2


MORE INFORMATION

The instances of this occurring are rare. The project file is not and does not become corrupt. To open the project, close all open projects and reopen the project in question.

Keywords: kbbug kbfix kbvbp500sp2fix kbvs97sp2fix KB171840