Article ID: 216853 - View products that this article applies to.
This article was previously published under Q216853
This article has been archived. It is offered "as is" and will no longer be updated.
A VBScript macro causes an application error in Msdev.exe when calling the Documents.Open method on a file that does not exist. This problem may occur, for example, if the file is managed by a source management system such as SourceSafe.
The file specified in the first Documents.Open parameter does not exist. The file may have been deleted or renamed on the local drive.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.This bug was corrected in Visual Studio 6.0 Service Pack 3. For more information about Visual Studio service packs, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/194022/ )Visual Studio 6.0 service packs, what, where, why
(https://support.microsoft.com/kb/194295/ )How to tell that Visual Studio 6.0 service packs are installed
The Documents.Open method takes three parameters:
If the file to be opened does not exist, VBScript throws a run-time exception error. The exception is normal and expected under this condition; however, Developer Studio does not handle it properly and faults internally.
Steps to reproduce the behavior
For more information about macros crashing Developer Studio, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/193478/ )FIX: Run-time macro errors cause Developer Studio to crash
Article ID: 216853 - Last Review: February 21, 2014 - Revision: 3.0