This article was previously published under Q315290
This article has been archived. It is offered "as is" and will no longer be updated.
When you use the WithEvents keyword to implement event procedures for a Visual Basic 6.0 WebClass, the events do not fire.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Visual Studio 6.0 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name Platform ----------------------------------------------------------------- 18-Dec-2001 11:44 220.127.116.1144 1,693,456 VBA6.dll x86 18-Dec-2001 11:47 18.104.22.168 1,884,160 VB6.exe x86
To apply this hotfix, follow these steps:
Locate the VB6.exe and VBA6.dll files on your computer. By default, these files are installed in the following folder:
Drive:\Program Files\Microsoft Visual Studio\VB98
Make sure that Visual Basic 6.0 is not running.
Make a backup copy of VB6.exe and VBA6.dll, and then replace them with the files from this hotfix.
NOTE: Because this is a compile-time problem, you must recompile all components that are affected after you apply this hotfix.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.