You can configure the Unattended Execution option and the Retained In Memory option in the latest version of Msvbvm60.dll (307211)
The information in this article applies to:
- Microsoft Visual Basic Enterprise Edition for Windows 6.0
- Microsoft Visual Basic Enterprise Edition for Windows 6.0 SP3
- Microsoft Visual Basic Enterprise Edition for Windows 6.0 SP4
- Microsoft Visual Basic Enterprise Edition for Windows 6.0 SP5
- Microsoft Visual Basic Professional Edition for Windows 6.0
This article was previously published under Q307211 SUMMARYYou must turn on the Unattended
Execution option and the Retained In Memory option before compilation to host a Microsoft Visual Basic Enterprise Edition for Windows 6.0 component
(Microsoft ActiveX DLL) in a multi-threaded environment, such as Microsoft Transaction Server (Mtx.exe),
Internet Information Services (Inetinfo.exe), COM+ (Dllhost.exe), and Microsoft SQL Server 7.0 or SQL Server 2000 (Sqlservr.exe). However, you may
not know whether a component is going to be used in such an
environment or you may forget to turn on the Unattended Execution option and the
Retained In Memory option. To address this problem, the latest
version of the Visual Basic runtime (Msvbvm60.dll) introduces a new feature
that permits you to turn on the Unattended
Execution option and the Retained In Memory option at run time. This article discusses how to configure these
options and what to be aware of when you turn on
these options at run time. Even with a .cfg file, a Visual Basic 6.0 component that you intend to use in Internet Information Services, in COM+, or in any multi-threaded
environment with a dynamic thread pool must not include any user interface elements. For example, the component must not include Visual Basic 6.0 forms or Visual Basic 6.0 controls.
Note A dynamic thread pool is a thread pool that repeatedly creates threads
and repeatedly destroys threads.
The
forms and the controls that are included with Visual Basic 6.0 and that are designed with Visual Basic 6.0
are intended to be used in applications that are single-threaded or in applications that are
multi-threaded without a dynamic thread pool. If you use user interface elements in a multi-threaded environment with a dynamic thread pool, unpredictable behavior may occur, including deadlocks. REFERENCES
For more information about how to obtain the latest
version of Msvbvm60.dll, click the following article number to view the article in the Microsoft Knowledge Base:
823746
Windows Server 2003 includes a new version of Msvbvm60.dll
For more information about threading with Visual Basic 6.0 ActiveX components, click the following article number to view the article in the Microsoft Knowledge Base:
241896
Threading issues with Visual Basic 6.0 ActiveX components
290887 VBRun60sp6.exe installs Visual Basic 6.0 SP6 run-time files
To obtain Visual Basic 6.0 Service Pack 6, visit the following Microsoft Developer Network (MSDN) Web site:
Modification Type: | Minor | Last Reviewed: | 9/26/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbinfo kbpending KB307211 kbAudDeveloper |
---|
|