Article ID: 823746 - Last Review: February 22, 2005 - Revision: 3.0 Windows Server 2003 includes a new version of Msvbvm60.dllSUMMARYThe version of the Msvbvm60.dll file that is included with
Microsoft Windows Server 2003 is 6.0.96.90. It is a newer file version than the
Msvbvm60.dll file that is included with Microsoft Visual Studio 6.0 Service
Pack 5 (SP5). This article contains a link that you can use to download the latest available Microsoft Visual
Basic 6.0 runtime. It also lists the article numbers for the bugs that have been
fixed since the Visual Studio 6.0 SP6 version of the Msvbvm60.dll file was
released. Note Bug fixes for a particular component are cumulative and contain all the previous fixes for that component. Fixes with a particular version number contain all the fixes that have an earlier version number. For additional information about the latest Visual Studio service pack, click the following article number to view the article in the Microsoft Knowledge Base: 834001
(http://support.microsoft.com/kb/834001/
)
List of bugs that are fixed in Visual Studio 6.0 Service Pack 6
Note Visual Studio 6.0 Service Pack 6 contains the newest version of Msvbvm60.dll.
MORE INFORMATIONA compressed .cab file that contains a self-extracting
executable file is
available for download. To download this file, visit the following Microsoft Web site: http://activex.microsoft.com/controls/vb6/vbrun60.cab
(http://activex.microsoft.com/controls/vb6/vbrun60.cab)
This file installs the latest versions of the Visual Basic run-time files. All applications that are created with Visual Basic 6.0 require the latest versions of the Visual Basic
run-time files.VBRun60.exe installs the following core files. These files are included with Microsoft Visual Studio 6.0. These files are the base dependencies for any component or application that is created in Visual Basic 6.0: Collapse this table
Collapse this table
VBRun60.exe /?
For additional information about command-line arguments for this file, click the following article number to view the article in the Microsoft Knowledge Base:
189520
(http://support.microsoft.com/kb/189520/
)
Outlook Deployment Kit (ODK) Setup command-line options
To distribute this new version with the Package and Deployment Wizard (PDW), copy the new version of the Msvbvm60.dll file to the following file folder so that you can use it with the PDW: \Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\Redist The VBRun60.exe file is not intended to replace the PDW for distributing Visual Basic applications. For
example, if your application includes components such as ActiveX controls or
DLLs, use the PDW or a third-party setup package for distribution.
However, if your Visual Basic application only depends on the files that are included
in the VBRun60.exe file, you can distribute your application by providing end
users with the executable (.exe) file and with VBRun60.exe.To determine whether your application requires additional files for distribution, you can use the PDW to create a set of setup files as a test. When the PDW creates a setup package, the PDW also creates a Setup.lst file. You can open the Setup.lst file in any text editor (for example, Notepad). If the [Setup1 Files] section of the resulting Setup.lst file only lists your .exe file, an end user should be able to run your application after the user runs VBRun60.exe to install the core run-time files. However, if the [Setup1 Files] section contains multiple files, consider using the PDW or a third-party setup package for distribution instead. In addition to distributing simple executable files, you can use the VBRun60.exe file for the following:
Extract Vbrun60.cab
For additional information about using the Extract utility, click the following article number to view the article in the Microsoft Knowledge Base:
129605
(http://support.microsoft.com/kb/129605/
)
How to extract original compressed Windows files
REFERENCES
For additional information about the bugs that are fixed by the Windows XP
version of the Msvbvm60.dll file, click the following article numbers to view the articles in the Microsoft Knowledge Base:
291103
(http://support.microsoft.com/kb/291103/
)
BUG: InsertObjDlg method fails with "Unable to Access Source" error message
297108
(http://support.microsoft.com/kb/297108/
)
BUG: Visual Basic SendKeys causes incorrect keyboard status or freezes keyboard
326345
(http://support.microsoft.com/kb/326345/
)
"Invalid Procedure Call" error message or access violation when you try to assign user-defined type to variant
300850
(http://support.microsoft.com/kb/300850/
)
BUG:
GlobalMultiUse class does not terminate in multithreaded
environment
308644
(http://support.microsoft.com/kb/308644/
)
BUG: Memory leak when you bind a recordset to Visual Basic intrinsic controls
312218
(http://support.microsoft.com/kb/312218/
)
BUG: Deadlock in multithreaded process if you use declare statements for APIs in Visual Basic ActiveX .dll files or .ocx files
321055
(http://support.microsoft.com/kb/321055/
)
Deadlock may occur when you use Printer object in a multithreaded application
325568
(http://support.microsoft.com/kb/325568/
)
WM_WININICHANGE message causes a deadlock in multithreaded Visual Basic 6.0 applications
326264
(http://support.microsoft.com/kb/326264/
)
FIX: Microsoft Excel and Microsoft Word that have user controls stop responding when you save or print
327574
(http://support.microsoft.com/kb/327574/
)
FIX: ListBox extended matching does not work for Hebrew or Czech characters
| Article Translations
|
Back to the top
