BUG: Access Violation after Using VSS Add-In to Check a Class Module Out and Back In (241884)


The information in this article applies to:

  • Microsoft Visual Studio, Enterprise Edition 6.0
  • Microsoft Visual Studio 6.0 SP3
  • Microsoft Visual Basic Professional Edition for Windows 6.0
  • Microsoft Visual Basic Enterprise Edition for Windows 6.0
This article was previously published under Q241884

SYMPTOMS

In very large Visual Basic projects containing numerous class modules, after checking a class module out of the database through Visual Source Safe (VSS) add-in then checking it back in and running the project, the following error occurs:
The instruction at "0x0fafa8e8" referenced memory at "0x0000004e". The memory could not be "read." Click on OK to terminate the program. Click on CANCEL to debug the program.
The stack trace displays a VBA6.DLL function on top of the stack.

RESOLUTION

To workaround this problem, disable the Background Compile option by following the steps below:
  1. From the Tools menu, select Options.
  2. Select the General tab.
  3. Inside the Compile frame, deselect the Background Compile option.
  4. Save the project.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
Modification Type:MinorLast Reviewed:8/15/2005
Keywords:kbBug kbCompiler kbpending KB241884
©2004 Microsoft Corporation. All rights reserved.