Microsoft KB Archive/241884

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

Article ID: 241884

Article Last Modified on 8/15/2005

-

APPLIES TO


 * Microsoft Visual Studio 6.0 Enterprise Edition
 * Microsoft Visual Studio 6.0 Service Pack 3
 * Microsoft Visual Basic 6.0 Professional Edition
 * Microsoft Visual Basic 6.0 Enterprise Edition

-



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.

Additional query words: Access Violation

Keywords: kbbug kbpending kbcompiler KB241884

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.