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

ID: Q241884

The information in this article applies to:

Microsoft Visual Studio, Enterprise Edition versions 6.0, 6.0 SP3

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:

From the Tools menu, select Options.

Select the General tab.

Inside the Compile frame, deselect the Background Compile option.

Save the project.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

Additional query words: Access Violation

Keywords : kbCompiler kbVBp600bug kbGrpVB kbDSupport
Version : WINDOWS:6.0,6.0 SP3
Platform : WINDOWS
Issue type : kbbug