The files include the fixes shipped with Service Pack 6 for Visual Basic 6.0. Visual Basic Runtime Files 6.0 SP6 on 32-bit and 64-bit PCs. This download is licensed as freeware for the Windows (32-bit and 64-bit) operating system on a laptop or desktop PC from components without restrictions.
- Visual Basic 6.0 Runtime Sp6 32 Bit Download
- Visual Basic 6.0 Runtime Sp6 32 Bit File
- Visual Basic 6.0 Runtime Sp6 32 Bit Mac
- Visual Basic 6.0 Runtime Sp6 32 Bit Download
- Visual Basic 6.0 Runtime Sp6 32 Bits
Mar 05, 2021 The VB6 runtime will ship and will be supported in Windows 8.1 for the lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all components must be hosted in 32-bit application processes. Developers can think of the support story for Windows 8.1 as being the same as it is for Windows 7. .NET 6.0 downloads for Linux, macOS, and Windows.NET is a free, cross-platform, open-source developer platform for building many different types of applications. Visual basic 6.0 64 bit windows 8. Visual basic for windows 7 32 bit. Visual basic for windows 8 64 bit. Visual studio exe free download. Featured Jul 05, 2018. The Visual Basic team's goal is that Visual Basic 6.0 applications continue to run on supported Windows versions. Key Visual Basic 6.0 runtime files, used in the majority of application scenarios, are shipping in and supported in Windows.
-->
Note
The support policy below has been updated with Windows 10 version 20H2 support information.
Executive summary
The Visual Basic team is committed to 'It Just Works' compatibility for Visual Basic 6.0 applications on the following supported Windows operating systems:
- Windows 10
- Windows 8.1
- Windows 7
- Windows Server 2019
- Windows Server 2016
- Windows Server 2012 including R2
- Windows Server 2008 including R2
The Visual Basic team's goal is that Visual Basic 6.0 applications continue to run on supported Windows versions. As detailed in this document, the core Visual Basic 6.0 runtime will be supported for the full lifetime of supported Windows versions, which is five years of mainstream support followed by five years of extended support (https://support.microsoft.com/gp/lifepolicy). The support bar will be limited to serious regressions and critical security issues for existing applications. For additional information and product documentation, see the Visual Basic 6.0 Resource Center.
Technical summary
Visual Basic 6.0 is made up of these key deliverables:
- Visual Basic 6.0 IDE (Integrated Development Environment).
- Visual Basic 6.0 Runtime: the base libraries and execution engine used to run VB 6.0 applications.
- Visual Basic 6.0 Runtime Extended Files: selected ActiveX control OCX files, libraries, and tools shipping with the IDE media and as an online release.
The Visual Basic 6.0 IDE
The Visual Basic 6.0 IDE is no longer supported as of April 8, 2008. Additionally, both the Windows and Visual Basic teams have tested Visual Basic 6.0 IDE on Windows Vista, Windows 7, Windows Server 2008, Windows 8, and Windows 8.1 to understand and mitigate (if appropriate) compatibility issues on 32-bit versions of Windows (see the 64-Bit Windows section below for further information about 64-bit systems). This announcement does not change the support policy for the IDE.
The Visual Basic 6.0 runtime
The Visual Basic 6.0 runtime is defined as the compiled binary files originally included in the redistribution list for Visual Basic 6.0. These files were marked as distributable in the original Visual Basic 6.0 license. Examples of these files include the Visual Basic 6.0 runtime library (msvbvm60.dll), controls (i.e., msflxgrd.ocx) along with runtime support files for other major functional areas (i.e. MDAC).
The runtime is divided into the three groups:
Supported runtime files -- Shipping in the OS
Key Visual Basic 6.0 runtime files, used in the majority of application scenarios, are shipping in and supported for the lifetime of supported Windows versions. This lifetime is five years of mainstream support and five years of extended support from the time that a given version of Windows ships. These files have been tested for compatibility as part of our testing of Visual Basic 6.0 applications running on supported Windows versions.
Note
All supported Windows versions contain a nearly identical list of files, and the redist requirements for applications containing these files should be nearly identical. One key difference is that
TriEdit.dllwas removed from Windows Vista and later versions.Supported runtime files –- Extended files to distribute with your application
This extended list consists of key controls, libraries, and tools that are installed from the IDE media or from Microsoft.com to the developer machine. Typically, the VB6 IDE installed these controls to the developer machine by default. The developer still needs to redistribute these files with the application. The supported version of the files is available online on the Microsoft Download Center (https://go.microsoft.com/fwlink/?LinkID=142927).
Unsupported runtime files
Some files either have fallen out of mainstream support or were never included as a part of the runtime redist (e.g., they were included in the
Toolsfolder on the IDE media to support legacy VB4/VB5 applications, or they were third-party controls). These files are not supported on Windows; instead they are subject to whatever support agreement applies to the media they were shipped with. This implies no warranties around support and servicing. In some instances, later versions of these libraries are supported. Details on backward compatibility or migration to supported versions are provided below.
For specific details on the files included in each support group see the Runtime Definition section below.
The Visual Basic 6.0 support lifetime
Supporting and/or shipping Visual Basic 6.0 runtime binaries on supported Windows versions does not change the support policy for the Visual Basic 6.0 IDE or Visual Studio 6.0 IDE as a whole. Those products moved out of extended support on April 8, 2008.
Details on the support lifecycle of Microsoft products can be found at https://support.microsoft.com/gp/lifepolicy. As a part of this support lifecycle, Microsoft will continue to support the Visual Basic 6.0 runtime on supported Windows versions for the support lifetime of those operating systems. This means, for example, that the Visual Basic 6.0 runtime will be supported on Windows Server 2003 until June, 2008 for Mainstream Support and June, 2013 for Extended Support.For more details on the support lifecycle or to find out about additional support options, please visit our support page at https://www.microsoft.com/support.
Supported Windows operating system versions
This section provides additional information regarding the operating systems that offer some level of support for VB6.
| Windows operating system | VB6 Supported Runtime Files Shipping in Windows have support? | VB6 Supported Rutime Extended Files to distribute with your application have support? | VB6 IDE has support? |
|---|---|---|---|
| Windows 10, all 32-bit editions | Yes * | Yes * | No |
| Windows 10, all 64-bit editions (WOW only) | Yes * 32-bit apps running in WOW only | Yes* 32-bit apps running in WOW only | No |
| Windows 8.1, all 32-bit editions | Yes * | Yes * | No |
| Windows 8.1, all 64-bit editions (WOW only) | Yes * 32-bit apps running in WOW only | Yes* 32-bit apps running in WOW only | No |
| Windows 7, all 32-bit editions | Yes * | Yes * | No |
| Windows 7, all 64-bit editions (WOW only) | Yes * 32-bit apps running in WOW only | Yes * 32-bit apps running in WOW only | No |
| Windows Server 2019, all 64-bit editions (WOW only) | Yes* 32-bit apps running in WOW only | Yes* 32-bit apps running in WOW only | No |
| Windows Server 2016, all 64-bit editions (WOW only) | Yes* 32-bit apps running in WOW only | Yes* 32-bit apps running in WOW only | No |
| Windows Server 2012 R2, all 64-bit editions (WOW only) Windows Server 2012, all 64-bit editions (WOW only) | Yes* 32-bit apps running in WOW only | Yes* 32-bit apps running in WOW only | No |
| Windows Server 2008 R2, all x64 editions (WOW only) Windows Server 2008, all x64 editions (WOW only) | Yes * 32-bit apps running in WOW only | Yes * 32-bit apps running in WOW only | No |
| Windows Server 2008, all 32-bit editions | Yes * | Yes * | No |
Note
VB6 runtime support is limited by the Windows support lifecycle. For example, if the target OS is in Extended support, VB6 cannot have a higher level of support than Extended support. The Windows support lifecycle fact sheet contains additional lifecycle information about previous and current Windows versions.
64-Bit Windows
Visual Basic 6.0 runtime files are 32-bit. These files ship in 64-bit Windows Operating Systems referenced in the table below. 32-bit VB6 applications and components are supported in the WOW emulation environment only. 32-bit components must also be hosted in 32-bit application processes.
The Visual Basic 6.0 IDE has never been offered in a native 64-bit version, nor has the 32-bit IDE been supported on 64-bit Windows. VB6 development on 64-bit Windows or any native architecture other than 32-bit is not and will not be supported.
Windows 10
Since the initial release of this support statement, the Windows 10 operating system has been released. This document has been updated to clarify Microsoft's support for VB6 on Windows 10.
The VB6 runtime will ship and will be supported in Windows 10 for the lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all components must be hosted in 32-bit application processes. Developers can think of the support story for Windows 10 as being the same as it is for Windows 8.1.
Windows 8.1
Since the initial release of this support statement, the Windows 8.1 operating system has been released. This document has been updated to clarify Microsoft's support for VB6 on Windows 8.1.
The VB6 runtime will ship and will be supported in Windows 8.1 for the lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all components must be hosted in 32-bit application processes. Developers can think of the support story for Windows 8.1 as being the same as it is for Windows 7.
Windows 7
Since the initial release of this support statement, the Windows 7 operating system has been released. This document has been updated to clarify Microsoft's support for VB6 on Windows 7.
The VB6 runtime will ship and will be supported in Windows 7 for the lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all components must be hosted in 32-bit application processes.
Windows Server 2016
Since the initial release of this support statement, the Windows Server 2016 operating system has been released. This document has been updated to clarify Microsoft's support for VB6 on Windows Server 2016.
The VB6 runtime will ship and will be supported in Windows Server 2016 for the lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all components must be hosted in 32-bit application processes. Developers can think of the support story for Windows Server 2016 as being the same as it is for Windows Server 2012 R2.
Windows Server 2012 R2
Since the initial release of this support statement, the Windows Server 2012 R2 operating system has been released. This document has been updated to clarify Microsoft's support for VB6 on Windows Server 2012 R2.
The VB6 runtime will ship and will be supported in Windows Server 2012 R2 for the lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all components must be hosted in 32-bit application processes. Developers can think of the support story for Windows Server 2012 R2 as being the same as it is for Windows Server 2012.
Windows Server 2012
Since the initial release of this support statement, the Windows Server 2012 operating system has been released. This document has been updated to clarify Microsoft's support for VB6 on Windows Server 2012.
The VB6 runtime will ship and will be supported in Windows Server 2012 for the lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all components must be hosted in 32-bit application processes. Developers can think of the support story for Windows Server 2012 as being the same as it is for Windows Server 2008 R2.
Windows Server 2008 R2
Since the initial release of this support statement, the Windows Server 2008 R2 operating system has been released. This document has been updated to clarify Microsoft's support for VB6 on Windows Server 2008 R2.
The VB6 runtime will ship and will be supported in Windows Server 2008 R2 for the lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all components must be hosted in 32-bit application processes. Developers can think of the support story for Windows Server 2008 R2 as being the same as it is for Windows Server 2008.
Windows Server 2008
Since the initial release of this support statement, the Windows Server 2008 operating system has been released. This document has been updated to clarify Microsoft's support for VB6 on Windows Server 2008.
The VB6 runtime will ship and will be supported in Windows Server 2008 for the lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all components must be hosted in 32-bit application processes.
Visual Basic 6.0 runtime usage inside VBA and Office
Visual Basic for Applications, or VBA, is a distinct technology commonly used for application automation and macros inside of other applications, most commonly inside Microsoft Office applications. VBA ships as a part of Office and therefore the support for VBA is governed by the support policy of Office. However, there are situations where VBA is used to call or host Visual Basic 6.0 runtime binaries and controls. In these situations, Visual Basic 6.0 supported runtime files in the OS and the extended file list are also supported when used inside of a supported VBA environment.
For VB6 runtime scenarios to be supported inside VBA, all of the following must be true:
- The host OS version for VB runtime is still supported.
- The host version of Office for VBA is still supported.
- The runtime files in question are still supported.
Visual Basic Script (VBScript)
VBScript is unrelated to Visual Basic 6.0 and this support statement. However, VBScript is currently shipping as part of Windows 7, Windows 8.1, Windows 10, Windows Server 2008 including R2, Windows Server 2012 including R2, and Windows Server 2016 and is governed by the OS support lifecycle.
Third-party components
Microsoft is unable to provide support for third party components, such as OCX/ActiveX controls. Customers are encouraged to contact the original control vendor for details on support for those components.
Reporting issues with VB 6.0 applications running on Windows
Developers planning to use Visual Basic 6.0 with one of the listed Windows operating systems should install that operating system and begin application compatibility testing using original application acceptance testing.
If you find an issue with your Visual Basic 6.0 application running on one of the listed Windows operating systems, please follow your normal support channels to report the issue.
Runtime definition
Runtime files supported and shipping in Windows
| atl.dll | msadcor.dll | msvbvm60.dll | ole2.dll |
| asycfilt.dll | msadds.dll | msvcirt.dll | ole32.dll |
| comcat.dll | msaddsr.dll | msvcrt.dll | oleaut32.dll |
| compobj.dll | msader15.dll | msvcrt40.dll | oleaut32.dll |
| dbnmpntw.dll | msado15.dll | mtxdm.dll | oledb32.dll |
| dcomcnfg.exe | msador15.dll | mtxoci.dll | oledb32r.dll |
| dllhost.exe | msadrh15.dll | odbc16gt.dll | oledlg.dll |
| ds16gt.dll | mscpxl32.dll | odbc32.dll | olepro32.dll |
| ds32gt.dll | msdadc.dll | odbc32gt.dll | olethk32.dll |
| expsrv.dll | msdaenum.dll | odbcad32.exe | regsvr32.exe |
| hh.exe | msdaer.dll | odbccp32.dll | rpcns4.dll |
| hhctrl.ocx | msdaora.dll | odbccr32.dll | rpcrt4.dll |
| imagehlp.dll | msdaosp.dll | odbccu32.dll | scrrun.dll |
| iprop.dll | msdaprst.dll | odbcint.dll | secur32.dll |
| itircl.dll | msdaps.dll | odbcji32.dll | simpdata.tlb |
| itss.dll | msdasc.dll | odbcjt32.dll | sqloledb.dll |
| mfc40.dll | msdasql.dll | odbctrac.dll | sqlsrv32.dll |
| mfc42.dll | msdasqlr.dll | oddbse32.dll | stdole2.tlb |
| mfc42u.dll | msdatsrc.tlb | odexl32.dll | stdole32.tlb |
| msadce.dll | msdatt.dll | odfox32.dll | storage.dll |
| msadcer.dll | msjtes40.dll | odpdx32.dll | vbajet32.dll |
| msadco.dll | msorcl32.dll | odtext32.dll |
Note
The files ds16gt.dll, ds32gt.dll, odbc16gt.dll, and odbc32gt.dll are only supported on a 32-bit OS.
Supported runtime files to distribute with your application
| comct232.ocx | msbind.dll | msdbrptr.dll | msstdfmt.dll |
| comct332.ocx | mscdrun.dll | msflxgrd.ocx | msstkprp.dll |
| comctl32.ocx | mschrt20.ocx | mshflxgd.ocx | mswcrun.dll |
| comdlg32.ocx | mscomct2.ocx | mshtmpgr.dll | mswinsck.ocx |
| dbadapt.dll | mscomctl.ocx | msinet.ocx | picclp32.ocx |
| dbgrid32.ocx | mscomm32.ocx | msmapi32.ocx | richtx32.ocx |
| dblist32.ocx | msdatgrd.ocx | msmask32.ocx | sysinfo.ocx |
| mci32.ocx | msdatlst.ocx | msrdc20.ocx | tabctl32.ocx |
| msadodc.ocx | msdatrep.ocx | msrdo20.dll |
Unsupported, but supported and compatible updates or upgrades are available
| dao350.dll | msexch35.dll | msjter35.dll | msrepl35.dll |
| mdac_typ.exe | msexcl35.dll | msjtor35.dll | mstext35.dll |
| mschart.ocx | msjet35.dll | msltus35.dll | msxbse35.dll |
| msdaerr.dll | msjint35.dll | mspdox35.dll | odbctl32.dll |
| msdatl2.dll | msjt4jlt.dll | msrd2x35.dll | oledb32x.dll |
Unsupported runtime files
| anibtn32.ocx | spin32.ocx | rpcltscm.dll | rdocurs.dll |
| graph32.ocx | gauge32.ocx | rpcmqcl.dll | vbar332.dll |
| keysta32.ocx | gswdll32.dll | rpcmqsvr.dll | visdata.exe |
| autmgr32.exe | ciscnfg.exe | rpcss.exe | vsdbflex.srg |
| autprx32.dll | olecnv32.dll | dbmsshrn.dll | threed32.ocx |
| racmgr32.exe | rpcltc1.dll | dbmssocn.dll | MSWLess.ocx |
| racreg32.dll | rpcltc5.dll | windbver.exe | tlbinf32.dll |
| grid32.ocx | rpcltccm.dll | msderun.dll | triedit.dll |
| msoutl32.ocx | rpclts5.dll | odkob32.dll |
Localization support binaries
The following binaries are necessary for supporting Visual Basic 6.0 applications running on localized versions of the Windows operating system. They are supported but are not shipped in Windows. These files are required to be shipped with your application setup.
Supported runtime files to distribute with your application
| JPN | KOR | CHT | CHS |
|---|---|---|---|
| mfc42jpn.dll | mfc42kor.dll | mfc42cht.dll | mfc42chs.dll |
| scrrnjp.dll | scrrnko.dll | scrrncht.dll | scrrnchs.dll |
| vb6jp.dll | vb6ko.dll | vb6cht.dll | vb6chs.dll |
| cmct2jp.dll | cmct2ko.dll | cmct2cht.dll | cmct2chs.dll |
| cmct3jp.dll | cmct3ko.dll | cmct3cht.dll | mscc2chs.dll |
| mscc2jp.dll | mscc2ko.dll | mscc2cht.dll | cmct3chs.dll |
| cmctljp.dll | cmctlko.dll | cmctlcht.dll | cmctlchs.dll |
| cmdlgjp.dll | cmdlgko.dll | mscmccht.dll | mscmcchs.dll |
| mscmcjp.dll | mscmcko.dll | cmdlgcht.dll | cmdlgchs.dll |
| dbgrdjp.dll | dbgrdko.dll | dbgrdcht.dll | dbgrdchs.dll |
| dblstjp.dll | dblstko.dll | dblstcht.dll | dblstchs.dll |
| mcijp.dll | mciko.dll | mcicht.dll | mcichs.dll |
| msadnjp.dll | msadnko.dll | msadncht.dll | msadnchs.dll |
| adodcjp.dll | adodcko.dll | adodccht.dll | adodcchs.dll |
| mschtjp.dll | mschtko.dll | mschtcht.dll | mschtchs.dll |
| msch2jp.dll | msch2ko.dll | msch2cht.dll | msch2chs.dll |
| mscomjp.dll | mscomko.dll | mscomcht.dll | mscomchs.dll |
| datgdjp.dll | datgdko.dll | datgdcht.dll | datgdchs.dll |
| datlsjp.dll | datlsko.dll | datlscht.dll | datlschs.dll |
| datrpjp.dll | datrpko.dll | datrpcht.dll | datrpchs.dll |
| dbrprjp.dll | dbrprko.dll | dbrprcht.dll | dbrprchs.dll |
| flxgdjp.dll | flxgdko.dll | flxgdcht.dll | flxgdchs.dll |
| mshfgjpn.dll | mshfgkor.dll | mshfgcht.dll | mshfgchs.dll |
| htmprjp.dll | htmprko.dll | htmprcht.dll | htmprchs.dll |
| inetjp.dll | inetko.dll | inetcht.dll | inetchs.dll |
| msmpijp.dll | msmpiko.dll | msmpicht.dll | msmpichs.dll |
| msmskjp.dll | msmskko.dll | msmskcht.dll | msmskchs.dll |
| rdc20jp.dll | rdc20ko.dll | rdc20cht.dll | rdc20chs.dll |
| rdo20jp.dll | rdo20ko.dll | rdo20cht.dll | rdo20chs.dll |
| stdftjp.dll | stdftko.dll | stdftcht.dll | stdftchs.dll |
| mswcrjp.dll | mswcrko.dll | mswcrcht.dll | mswcrchs.dll |
| winskjp.dll | winskko.dll | winskcht.dll | winskchs.dll |
| pcclpjp.dll | pcclpko.dll | pcclpcht.dll | pcclpchs.dll |
| rchtxjp.dll | rchtxko.dll | rchtxcht.dll | rchtxchs.dll |
| sysinjp.dll | sysinko.dll | sysincht.dll | sysinchs.dll |
| tabctjp.dll | tabctko.dll | tabctcht.dll | tabctchs.dll |
| ITA | FRA | ESP | DEU |
|---|---|---|---|
| mfc42ita.dll | mfc42fra.dll | mfc42esp.dll | mfc42deu.dll |
| scrrnit.dll | scrrnfr.dll | scrrnes.dll | scrrnde.dll |
| vb6it.dll | vb6fr.dll | vb6es.dll | vb6de.dll |
| cmct2it.dll | cmct2fr.dll | cmct2es.dll | cmct2de.dll |
| mscc2it.dll | mscc2fr.dll | mscc2es.dll | mscc2de.dll |
| cmct3it.dll | cmct3fr.dll | cmct3es.dll | cmct3de.dll |
| cmctlit.dll | cmctlfr.dll | cmctles.dll | cmctlde.dll |
| mscmcit.dll | mscmcfr.dll | mscmces.dll | mscmcde.dll |
| cmdlgit.dll | cmdlgfr.dll | cmdlges.dll | cmdlgde.dll |
| dbgrdit.dll | dbgrdfr.dll | dbgrdes.dll | dbgrdde.dll |
| dblstit.dll | dblstfr.dll | dblstes.dll | dblstde.dll |
| mciit.dll | mcifr.dll | mcies.dll | mcide.dll |
| msadnit.dll | msadnfr.dll | msadnes.dll | msadnde.dll |
| adodcit.dll | adodcfr.dll | adodces.dll | adodcde.dll |
| mschtit.dll | mschtfr.dll | mschtes.dll | mschtde.dll |
| msch2it.dll | msch2fr.dll | msch2es.dll | msch2de.dll |
| mscomit.dll | mscomfr.dll | mscomes.dll | mscomde.dll |
| atgdit.dll | datgdfr.dll | datgdes.dll | datgdde.dll |
| datlsit.dll | datlsfr.dll | datlses.dll | datlsde.dll |
| datrpit.dll | datrpfr.dll | datrpes.dll | datrpde.dll |
| dbrprit.dll | dbrprfr.dll | dbrpres.dll | dbrprde.dll |
| flxgdit.dll | flxgdfr.dll | flxgdes.dll | flxgdde.dll |
| mshfgit.dll | mshfgfr.dll | mshfges.dll | mshfgde.dll |
| htmprit.dll | htmprfr.dll | htmpres.dll | htmprde.dll |
| inetit.dll | inetfr.dll | inetes.dll | inetde.dll |
| msmpiit.dll | msmpifr.dll | msmpies.dll | msmpide.dll |
| msmskit.dll | msmskfr.dll | msmskes.dll | msmskde.dll |
| rdc20it.dll | rdc20fr.dll | rdc20es.dll | rdc20de.dll |
| rdo20it.dll | rdo20fr.dll | rdo20es.dll | rdo20de.dll |
| stdftit.dll | stdftfr.dll | stdftes.dll | stdftde.dll |
| mswcrit.dll | mswcrfr.dll | mswcres.dll | mswcrde.dll |
| winskit.dll | winskfr.dll | winskes.dll | winskde.dll |
| pcclpit.dll | pcclpfr.dll | pcclpes.dll | pcclpde.dll |
| rchtxit.dll | rchtxfr.dll | rchtxes.dll | rchtxde.dll |
| sysinit.dll | sysinfr.dll | sysines.dll | sysinde.dll |
| tabctit.dll | tabctfr.dll | tabctes.dll | tabctde.dll |
See Also
Visual Basic 6.0 Runtime Sp6 32 Bit Download
It looks like the Visual Basic 6 holdouts can breathe yet another sigh of relief. Visual Basic 6 seems to work with Windows 10 as do VB6 apps, though not without some caveats.
I've been reading a few threads in various forums where most people have had few to no problems developing VB6 apps or running them in Windows 10. I've seen at least one VB6 developer that claims they're OCX laden application has issues when loading. They say that some of the controls simply fail to load at runtime. Funny enough, it happens only on 32 bit Windows and 64 bit Windows 10 works fine. They gave no information if these were new installs or legacy upgrades.
Visual Basic 6.0 Runtime Sp6 32 Bit File
Another developer claims to have problems installing VB6 Service Pack 6 on Windows 10. They tracked it down to two Registry keys not being written. This website gives a process to install VB6 in Windows 10. The fact there is now a procedure to install an old app on a new operating system should be pause for concern.
Note
The support policy below has been updated with Windows 10 version 20H2 support information.
Executive summary
The Visual Basic team is committed to 'It Just Works' compatibility for Visual Basic 6.0 applications on the following supported Windows operating systems:
- Windows 10
- Windows 8.1
- Windows 7
- Windows Server 2019
- Windows Server 2016
- Windows Server 2012 including R2
- Windows Server 2008 including R2
The Visual Basic team's goal is that Visual Basic 6.0 applications continue to run on supported Windows versions. As detailed in this document, the core Visual Basic 6.0 runtime will be supported for the full lifetime of supported Windows versions, which is five years of mainstream support followed by five years of extended support (https://support.microsoft.com/gp/lifepolicy). The support bar will be limited to serious regressions and critical security issues for existing applications. For additional information and product documentation, see the Visual Basic 6.0 Resource Center.
Technical summary
Visual Basic 6.0 is made up of these key deliverables:
- Visual Basic 6.0 IDE (Integrated Development Environment).
- Visual Basic 6.0 Runtime: the base libraries and execution engine used to run VB 6.0 applications.
- Visual Basic 6.0 Runtime Extended Files: selected ActiveX control OCX files, libraries, and tools shipping with the IDE media and as an online release.
The Visual Basic 6.0 IDE
The Visual Basic 6.0 IDE is no longer supported as of April 8, 2008. Additionally, both the Windows and Visual Basic teams have tested Visual Basic 6.0 IDE on Windows Vista, Windows 7, Windows Server 2008, Windows 8, and Windows 8.1 to understand and mitigate (if appropriate) compatibility issues on 32-bit versions of Windows (see the 64-Bit Windows section below for further information about 64-bit systems). This announcement does not change the support policy for the IDE.
The Visual Basic 6.0 runtime
The Visual Basic 6.0 runtime is defined as the compiled binary files originally included in the redistribution list for Visual Basic 6.0. These files were marked as distributable in the original Visual Basic 6.0 license. Examples of these files include the Visual Basic 6.0 runtime library (msvbvm60.dll), controls (i.e., msflxgrd.ocx) along with runtime support files for other major functional areas (i.e. MDAC).
The runtime is divided into the three groups:
Supported runtime files -- Shipping in the OS
Key Visual Basic 6.0 runtime files, used in the majority of application scenarios, are shipping in and supported for the lifetime of supported Windows versions. This lifetime is five years of mainstream support and five years of extended support from the time that a given version of Windows ships. These files have been tested for compatibility as part of our testing of Visual Basic 6.0 applications running on supported Windows versions.
Note
All supported Windows versions contain a nearly identical list of files, and the redist requirements for applications containing these files should be nearly identical. One key difference is that
TriEdit.dllwas removed from Windows Vista and later versions.Supported runtime files –- Extended files to distribute with your application
This extended list consists of key controls, libraries, and tools that are installed from the IDE media or from Microsoft.com to the developer machine. Typically, the VB6 IDE installed these controls to the developer machine by default. The developer still needs to redistribute these files with the application. The supported version of the files is available online on the Microsoft Download Center (https://go.microsoft.com/fwlink/?LinkID=142927).
Unsupported runtime files
Some files either have fallen out of mainstream support or were never included as a part of the runtime redist (e.g., they were included in the
Toolsfolder on the IDE media to support legacy VB4/VB5 applications, or they were third-party controls). These files are not supported on Windows; instead they are subject to whatever support agreement applies to the media they were shipped with. This implies no warranties around support and servicing. In some instances, later versions of these libraries are supported. Details on backward compatibility or migration to supported versions are provided below.
For specific details on the files included in each support group see the Runtime Definition section below.
The Visual Basic 6.0 support lifetime
Supporting and/or shipping Visual Basic 6.0 runtime binaries on supported Windows versions does not change the support policy for the Visual Basic 6.0 IDE or Visual Studio 6.0 IDE as a whole. Those products moved out of extended support on April 8, 2008.
Details on the support lifecycle of Microsoft products can be found at https://support.microsoft.com/gp/lifepolicy. As a part of this support lifecycle, Microsoft will continue to support the Visual Basic 6.0 runtime on supported Windows versions for the support lifetime of those operating systems. This means, for example, that the Visual Basic 6.0 runtime will be supported on Windows Server 2003 until June, 2008 for Mainstream Support and June, 2013 for Extended Support.For more details on the support lifecycle or to find out about additional support options, please visit our support page at https://www.microsoft.com/support.
Supported Windows operating system versions
This section provides additional information regarding the operating systems that offer some level of support for VB6.
| Windows operating system | VB6 Supported Runtime Files Shipping in Windows have support? | VB6 Supported Rutime Extended Files to distribute with your application have support? | VB6 IDE has support? |
|---|---|---|---|
| Windows 10, all 32-bit editions | Yes * | Yes * | No |
| Windows 10, all 64-bit editions (WOW only) | Yes * 32-bit apps running in WOW only | Yes* 32-bit apps running in WOW only | No |
| Windows 8.1, all 32-bit editions | Yes * | Yes * | No |
| Windows 8.1, all 64-bit editions (WOW only) | Yes * 32-bit apps running in WOW only | Yes* 32-bit apps running in WOW only | No |
| Windows 7, all 32-bit editions | Yes * | Yes * | No |
| Windows 7, all 64-bit editions (WOW only) | Yes * 32-bit apps running in WOW only | Yes * 32-bit apps running in WOW only | No |
| Windows Server 2019, all 64-bit editions (WOW only) | Yes* 32-bit apps running in WOW only | Yes* 32-bit apps running in WOW only | No |
| Windows Server 2016, all 64-bit editions (WOW only) | Yes* 32-bit apps running in WOW only | Yes* 32-bit apps running in WOW only | No |
| Windows Server 2012 R2, all 64-bit editions (WOW only) Windows Server 2012, all 64-bit editions (WOW only) | Yes* 32-bit apps running in WOW only | Yes* 32-bit apps running in WOW only | No |
| Windows Server 2008 R2, all x64 editions (WOW only) Windows Server 2008, all x64 editions (WOW only) | Yes * 32-bit apps running in WOW only | Yes * 32-bit apps running in WOW only | No |
| Windows Server 2008, all 32-bit editions | Yes * | Yes * | No |
Note
VB6 runtime support is limited by the Windows support lifecycle. For example, if the target OS is in Extended support, VB6 cannot have a higher level of support than Extended support. The Windows support lifecycle fact sheet contains additional lifecycle information about previous and current Windows versions.
64-Bit Windows
Visual Basic 6.0 runtime files are 32-bit. These files ship in 64-bit Windows Operating Systems referenced in the table below. 32-bit VB6 applications and components are supported in the WOW emulation environment only. 32-bit components must also be hosted in 32-bit application processes.
The Visual Basic 6.0 IDE has never been offered in a native 64-bit version, nor has the 32-bit IDE been supported on 64-bit Windows. VB6 development on 64-bit Windows or any native architecture other than 32-bit is not and will not be supported.
Windows 10
Since the initial release of this support statement, the Windows 10 operating system has been released. This document has been updated to clarify Microsoft's support for VB6 on Windows 10.
The VB6 runtime will ship and will be supported in Windows 10 for the lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all components must be hosted in 32-bit application processes. Developers can think of the support story for Windows 10 as being the same as it is for Windows 8.1.
Windows 8.1
Since the initial release of this support statement, the Windows 8.1 operating system has been released. This document has been updated to clarify Microsoft's support for VB6 on Windows 8.1.
The VB6 runtime will ship and will be supported in Windows 8.1 for the lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all components must be hosted in 32-bit application processes. Developers can think of the support story for Windows 8.1 as being the same as it is for Windows 7.
Windows 7
Since the initial release of this support statement, the Windows 7 operating system has been released. This document has been updated to clarify Microsoft's support for VB6 on Windows 7.
The VB6 runtime will ship and will be supported in Windows 7 for the lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all components must be hosted in 32-bit application processes.
Windows Server 2016
Since the initial release of this support statement, the Windows Server 2016 operating system has been released. This document has been updated to clarify Microsoft's support for VB6 on Windows Server 2016.
The VB6 runtime will ship and will be supported in Windows Server 2016 for the lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all components must be hosted in 32-bit application processes. Developers can think of the support story for Windows Server 2016 as being the same as it is for Windows Server 2012 R2.
Windows Server 2012 R2
Since the initial release of this support statement, the Windows Server 2012 R2 operating system has been released. This document has been updated to clarify Microsoft's support for VB6 on Windows Server 2012 R2.
The VB6 runtime will ship and will be supported in Windows Server 2012 R2 for the lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all components must be hosted in 32-bit application processes. Developers can think of the support story for Windows Server 2012 R2 as being the same as it is for Windows Server 2012.
Windows Server 2012
Since the initial release of this support statement, the Windows Server 2012 operating system has been released. This document has been updated to clarify Microsoft's support for VB6 on Windows Server 2012.
The VB6 runtime will ship and will be supported in Windows Server 2012 for the lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all components must be hosted in 32-bit application processes. Developers can think of the support story for Windows Server 2012 as being the same as it is for Windows Server 2008 R2.
Windows Server 2008 R2
Since the initial release of this support statement, the Windows Server 2008 R2 operating system has been released. This document has been updated to clarify Microsoft's support for VB6 on Windows Server 2008 R2.
The VB6 runtime will ship and will be supported in Windows Server 2008 R2 for the lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all components must be hosted in 32-bit application processes. Developers can think of the support story for Windows Server 2008 R2 as being the same as it is for Windows Server 2008.
Windows Server 2008
Since the initial release of this support statement, the Windows Server 2008 operating system has been released. This document has been updated to clarify Microsoft's support for VB6 on Windows Server 2008.
The VB6 runtime will ship and will be supported in Windows Server 2008 for the lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all components must be hosted in 32-bit application processes.
Visual Basic 6.0 runtime usage inside VBA and Office
Visual Basic for Applications, or VBA, is a distinct technology commonly used for application automation and macros inside of other applications, most commonly inside Microsoft Office applications. VBA ships as a part of Office and therefore the support for VBA is governed by the support policy of Office. However, there are situations where VBA is used to call or host Visual Basic 6.0 runtime binaries and controls. In these situations, Visual Basic 6.0 supported runtime files in the OS and the extended file list are also supported when used inside of a supported VBA environment.
For VB6 runtime scenarios to be supported inside VBA, all of the following must be true:
- The host OS version for VB runtime is still supported.
- The host version of Office for VBA is still supported.
- The runtime files in question are still supported.
Visual Basic Script (VBScript)
VBScript is unrelated to Visual Basic 6.0 and this support statement. However, VBScript is currently shipping as part of Windows 7, Windows 8.1, Windows 10, Windows Server 2008 including R2, Windows Server 2012 including R2, and Windows Server 2016 and is governed by the OS support lifecycle.
Third-party components
Microsoft is unable to provide support for third party components, such as OCX/ActiveX controls. Customers are encouraged to contact the original control vendor for details on support for those components.
Reporting issues with VB 6.0 applications running on Windows
Developers planning to use Visual Basic 6.0 with one of the listed Windows operating systems should install that operating system and begin application compatibility testing using original application acceptance testing.
If you find an issue with your Visual Basic 6.0 application running on one of the listed Windows operating systems, please follow your normal support channels to report the issue.
Runtime definition
Runtime files supported and shipping in Windows
| atl.dll | msadcor.dll | msvbvm60.dll | ole2.dll |
| asycfilt.dll | msadds.dll | msvcirt.dll | ole32.dll |
| comcat.dll | msaddsr.dll | msvcrt.dll | oleaut32.dll |
| compobj.dll | msader15.dll | msvcrt40.dll | oleaut32.dll |
| dbnmpntw.dll | msado15.dll | mtxdm.dll | oledb32.dll |
| dcomcnfg.exe | msador15.dll | mtxoci.dll | oledb32r.dll |
| dllhost.exe | msadrh15.dll | odbc16gt.dll | oledlg.dll |
| ds16gt.dll | mscpxl32.dll | odbc32.dll | olepro32.dll |
| ds32gt.dll | msdadc.dll | odbc32gt.dll | olethk32.dll |
| expsrv.dll | msdaenum.dll | odbcad32.exe | regsvr32.exe |
| hh.exe | msdaer.dll | odbccp32.dll | rpcns4.dll |
| hhctrl.ocx | msdaora.dll | odbccr32.dll | rpcrt4.dll |
| imagehlp.dll | msdaosp.dll | odbccu32.dll | scrrun.dll |
| iprop.dll | msdaprst.dll | odbcint.dll | secur32.dll |
| itircl.dll | msdaps.dll | odbcji32.dll | simpdata.tlb |
| itss.dll | msdasc.dll | odbcjt32.dll | sqloledb.dll |
| mfc40.dll | msdasql.dll | odbctrac.dll | sqlsrv32.dll |
| mfc42.dll | msdasqlr.dll | oddbse32.dll | stdole2.tlb |
| mfc42u.dll | msdatsrc.tlb | odexl32.dll | stdole32.tlb |
| msadce.dll | msdatt.dll | odfox32.dll | storage.dll |
| msadcer.dll | msjtes40.dll | odpdx32.dll | vbajet32.dll |
| msadco.dll | msorcl32.dll | odtext32.dll |
Note
The files ds16gt.dll, ds32gt.dll, odbc16gt.dll, and odbc32gt.dll are only supported on a 32-bit OS.
Supported runtime files to distribute with your application
| comct232.ocx | msbind.dll | msdbrptr.dll | msstdfmt.dll |
| comct332.ocx | mscdrun.dll | msflxgrd.ocx | msstkprp.dll |
| comctl32.ocx | mschrt20.ocx | mshflxgd.ocx | mswcrun.dll |
| comdlg32.ocx | mscomct2.ocx | mshtmpgr.dll | mswinsck.ocx |
| dbadapt.dll | mscomctl.ocx | msinet.ocx | picclp32.ocx |
| dbgrid32.ocx | mscomm32.ocx | msmapi32.ocx | richtx32.ocx |
| dblist32.ocx | msdatgrd.ocx | msmask32.ocx | sysinfo.ocx |
| mci32.ocx | msdatlst.ocx | msrdc20.ocx | tabctl32.ocx |
| msadodc.ocx | msdatrep.ocx | msrdo20.dll |
Unsupported, but supported and compatible updates or upgrades are available
| dao350.dll | msexch35.dll | msjter35.dll | msrepl35.dll |
| mdac_typ.exe | msexcl35.dll | msjtor35.dll | mstext35.dll |
| mschart.ocx | msjet35.dll | msltus35.dll | msxbse35.dll |
| msdaerr.dll | msjint35.dll | mspdox35.dll | odbctl32.dll |
| msdatl2.dll | msjt4jlt.dll | msrd2x35.dll | oledb32x.dll |
Unsupported runtime files
| anibtn32.ocx | spin32.ocx | rpcltscm.dll | rdocurs.dll |
| graph32.ocx | gauge32.ocx | rpcmqcl.dll | vbar332.dll |
| keysta32.ocx | gswdll32.dll | rpcmqsvr.dll | visdata.exe |
| autmgr32.exe | ciscnfg.exe | rpcss.exe | vsdbflex.srg |
| autprx32.dll | olecnv32.dll | dbmsshrn.dll | threed32.ocx |
| racmgr32.exe | rpcltc1.dll | dbmssocn.dll | MSWLess.ocx |
| racreg32.dll | rpcltc5.dll | windbver.exe | tlbinf32.dll |
| grid32.ocx | rpcltccm.dll | msderun.dll | triedit.dll |
| msoutl32.ocx | rpclts5.dll | odkob32.dll |
Localization support binaries
The following binaries are necessary for supporting Visual Basic 6.0 applications running on localized versions of the Windows operating system. They are supported but are not shipped in Windows. These files are required to be shipped with your application setup.
Supported runtime files to distribute with your application
| JPN | KOR | CHT | CHS |
|---|---|---|---|
| mfc42jpn.dll | mfc42kor.dll | mfc42cht.dll | mfc42chs.dll |
| scrrnjp.dll | scrrnko.dll | scrrncht.dll | scrrnchs.dll |
| vb6jp.dll | vb6ko.dll | vb6cht.dll | vb6chs.dll |
| cmct2jp.dll | cmct2ko.dll | cmct2cht.dll | cmct2chs.dll |
| cmct3jp.dll | cmct3ko.dll | cmct3cht.dll | mscc2chs.dll |
| mscc2jp.dll | mscc2ko.dll | mscc2cht.dll | cmct3chs.dll |
| cmctljp.dll | cmctlko.dll | cmctlcht.dll | cmctlchs.dll |
| cmdlgjp.dll | cmdlgko.dll | mscmccht.dll | mscmcchs.dll |
| mscmcjp.dll | mscmcko.dll | cmdlgcht.dll | cmdlgchs.dll |
| dbgrdjp.dll | dbgrdko.dll | dbgrdcht.dll | dbgrdchs.dll |
| dblstjp.dll | dblstko.dll | dblstcht.dll | dblstchs.dll |
| mcijp.dll | mciko.dll | mcicht.dll | mcichs.dll |
| msadnjp.dll | msadnko.dll | msadncht.dll | msadnchs.dll |
| adodcjp.dll | adodcko.dll | adodccht.dll | adodcchs.dll |
| mschtjp.dll | mschtko.dll | mschtcht.dll | mschtchs.dll |
| msch2jp.dll | msch2ko.dll | msch2cht.dll | msch2chs.dll |
| mscomjp.dll | mscomko.dll | mscomcht.dll | mscomchs.dll |
| datgdjp.dll | datgdko.dll | datgdcht.dll | datgdchs.dll |
| datlsjp.dll | datlsko.dll | datlscht.dll | datlschs.dll |
| datrpjp.dll | datrpko.dll | datrpcht.dll | datrpchs.dll |
| dbrprjp.dll | dbrprko.dll | dbrprcht.dll | dbrprchs.dll |
| flxgdjp.dll | flxgdko.dll | flxgdcht.dll | flxgdchs.dll |
| mshfgjpn.dll | mshfgkor.dll | mshfgcht.dll | mshfgchs.dll |
| htmprjp.dll | htmprko.dll | htmprcht.dll | htmprchs.dll |
| inetjp.dll | inetko.dll | inetcht.dll | inetchs.dll |
| msmpijp.dll | msmpiko.dll | msmpicht.dll | msmpichs.dll |
| msmskjp.dll | msmskko.dll | msmskcht.dll | msmskchs.dll |
| rdc20jp.dll | rdc20ko.dll | rdc20cht.dll | rdc20chs.dll |
| rdo20jp.dll | rdo20ko.dll | rdo20cht.dll | rdo20chs.dll |
| stdftjp.dll | stdftko.dll | stdftcht.dll | stdftchs.dll |
| mswcrjp.dll | mswcrko.dll | mswcrcht.dll | mswcrchs.dll |
| winskjp.dll | winskko.dll | winskcht.dll | winskchs.dll |
| pcclpjp.dll | pcclpko.dll | pcclpcht.dll | pcclpchs.dll |
| rchtxjp.dll | rchtxko.dll | rchtxcht.dll | rchtxchs.dll |
| sysinjp.dll | sysinko.dll | sysincht.dll | sysinchs.dll |
| tabctjp.dll | tabctko.dll | tabctcht.dll | tabctchs.dll |
| ITA | FRA | ESP | DEU |
|---|---|---|---|
| mfc42ita.dll | mfc42fra.dll | mfc42esp.dll | mfc42deu.dll |
| scrrnit.dll | scrrnfr.dll | scrrnes.dll | scrrnde.dll |
| vb6it.dll | vb6fr.dll | vb6es.dll | vb6de.dll |
| cmct2it.dll | cmct2fr.dll | cmct2es.dll | cmct2de.dll |
| mscc2it.dll | mscc2fr.dll | mscc2es.dll | mscc2de.dll |
| cmct3it.dll | cmct3fr.dll | cmct3es.dll | cmct3de.dll |
| cmctlit.dll | cmctlfr.dll | cmctles.dll | cmctlde.dll |
| mscmcit.dll | mscmcfr.dll | mscmces.dll | mscmcde.dll |
| cmdlgit.dll | cmdlgfr.dll | cmdlges.dll | cmdlgde.dll |
| dbgrdit.dll | dbgrdfr.dll | dbgrdes.dll | dbgrdde.dll |
| dblstit.dll | dblstfr.dll | dblstes.dll | dblstde.dll |
| mciit.dll | mcifr.dll | mcies.dll | mcide.dll |
| msadnit.dll | msadnfr.dll | msadnes.dll | msadnde.dll |
| adodcit.dll | adodcfr.dll | adodces.dll | adodcde.dll |
| mschtit.dll | mschtfr.dll | mschtes.dll | mschtde.dll |
| msch2it.dll | msch2fr.dll | msch2es.dll | msch2de.dll |
| mscomit.dll | mscomfr.dll | mscomes.dll | mscomde.dll |
| atgdit.dll | datgdfr.dll | datgdes.dll | datgdde.dll |
| datlsit.dll | datlsfr.dll | datlses.dll | datlsde.dll |
| datrpit.dll | datrpfr.dll | datrpes.dll | datrpde.dll |
| dbrprit.dll | dbrprfr.dll | dbrpres.dll | dbrprde.dll |
| flxgdit.dll | flxgdfr.dll | flxgdes.dll | flxgdde.dll |
| mshfgit.dll | mshfgfr.dll | mshfges.dll | mshfgde.dll |
| htmprit.dll | htmprfr.dll | htmpres.dll | htmprde.dll |
| inetit.dll | inetfr.dll | inetes.dll | inetde.dll |
| msmpiit.dll | msmpifr.dll | msmpies.dll | msmpide.dll |
| msmskit.dll | msmskfr.dll | msmskes.dll | msmskde.dll |
| rdc20it.dll | rdc20fr.dll | rdc20es.dll | rdc20de.dll |
| rdo20it.dll | rdo20fr.dll | rdo20es.dll | rdo20de.dll |
| stdftit.dll | stdftfr.dll | stdftes.dll | stdftde.dll |
| mswcrit.dll | mswcrfr.dll | mswcres.dll | mswcrde.dll |
| winskit.dll | winskfr.dll | winskes.dll | winskde.dll |
| pcclpit.dll | pcclpfr.dll | pcclpes.dll | pcclpde.dll |
| rchtxit.dll | rchtxfr.dll | rchtxes.dll | rchtxde.dll |
| sysinit.dll | sysinfr.dll | sysines.dll | sysinde.dll |
| tabctit.dll | tabctfr.dll | tabctes.dll | tabctde.dll |
See Also
Visual Basic 6.0 Runtime Sp6 32 Bit Download
It looks like the Visual Basic 6 holdouts can breathe yet another sigh of relief. Visual Basic 6 seems to work with Windows 10 as do VB6 apps, though not without some caveats.
I've been reading a few threads in various forums where most people have had few to no problems developing VB6 apps or running them in Windows 10. I've seen at least one VB6 developer that claims they're OCX laden application has issues when loading. They say that some of the controls simply fail to load at runtime. Funny enough, it happens only on 32 bit Windows and 64 bit Windows 10 works fine. They gave no information if these were new installs or legacy upgrades.
Visual Basic 6.0 Runtime Sp6 32 Bit File
Another developer claims to have problems installing VB6 Service Pack 6 on Windows 10. They tracked it down to two Registry keys not being written. This website gives a process to install VB6 in Windows 10. The fact there is now a procedure to install an old app on a new operating system should be pause for concern.
The only way to get hold of VB6 is to have a MSDN subscription. The subscription is $500 so that doesn't seem like a huge burden. But then again, remember that Microsoft is not supporting VB6 though the VB6 runtime is shipped with Windows 10.
There are a boatload of VB6 applications still out there so I think support for VB6 will be around for a long time. In April, 2014 an InfoQ article stated there were hundreds of VB6 developer positions listed on Dice and Monster. VB6 officially went out of support in 2008 so good luck finding entry level and even junior developers to fill those spots – no one is learning VB6 any more. One of my old clients has had a revolving door of VB6 developers for several years now and it's getting harder and harder to find competent VB6 developers, and developers that wish to work with it.
As a Xojo consultant we've converted quite a few VB6 apps. Well, convert is a strong word, really it's a rewrite. Despite both using a BASIC-like language, the two languages are diverging rapidly (not that they were ever really all that close to begin with). Many issues that we spent a lot of time working around in VB6 just don't happen in Xojo. In our experience entire modules and classes just disappear because we don't need them in Xojo.
Xojo is updated several times a year while VB6 isn't. Xojo is about ready to release a new version that creates 64 bit versions of Mac OS X, Windows, Linux for desktop, console, and web apps. iOS will also be 32 bit and 64 bit. VB6 is stuck building only 32 bit Windows apps.
Is Xojo a perfect alternative for VB6? No. It is not perfect for every application. Because its strength is really cross platform applications there are compromises all over the place. If you look at Mac and Linux applications they just don't have the complex controls that Windows does. For some this is a deal breaker because their application demands it. However, if you want a Mac OS X or Linux version of your application you'll want to redesign the UI anyway.
Ten years ago our clients came to us for Windows apps first and if we could do a Mac version for the graphics geek that was great. Now, they come to us for Mac apps first and if we can do a Windows version for the accountant in the corner that's great. Xojo does web apps now and that's become an increasingly larger portion of our business and VB6 just doesn't compete in that area.
The Xojo universe is full of VB6 developers and the Xojo forums are full of them. The developers that have found and started using Xojo usually go through a short learning curve and a few WTF moments. And then, after they stop trying to make Xojo work just like VB6, they embrace the tool and enjoy life again.
Visual Basic 6.0 Runtime Sp6 32 Bit Mac
Windows 10 is yet another bullet dodged for VB6 hold outs. At what point do you start to panic and find an alternative? I guess if you've waited this long you're hoping that Microsoft keeps supporting the VB6 runtime forever.
Visual Basic 6.0 Runtime Sp6 32 Bit Download
I am biased, naturally, but Xojo really is a good product and a good solution for many applications. If you would like to find out some rough costs of moving your application to Xojo we have a utility that will give us some metrics on your VB6 project. It can be found at http://www.bkeeney.com/vb2rbconversion/
Visual Basic 6.0 Runtime Sp6 32 Bits
Happy coding!
