Thursday, August 17, 2017

GetAdaptersInfo

This sample program makes some basic use of the API call and the results it returns to report on network adapters in your system. If you need more information you can easily expand upon it to extract multiple IP addresses where they exist, etc.

There are some limitations when using early versions of Windows, so see the MSDN if you need support for Windows XP or earlier.

Sample output, Adapter 0 is not connected to a network:

Download from me

Download from source



Source: VBForums

Sunday, July 30, 2017

Rendering of Nodes in a Graph

Rendering of Nodes in a Graph


Olaf is a genius who gave us much VB6 + ASM projects over the years. Below is an advanced VB6 project + the vbRichClient5 library. If you ask what is this vbRichClient5 library, I can tell you that vbRichClient5 is a VB6 package that puts all programming languages at the corner of shame. Maybe Microsoft does not update VB6, but, super-advanced programmers like Olaf put Microsoft programmers at the corner of shame. I'm glad to have you among us Olaf !

This cairo-(vbRichClient5)-dependent Demo will show (as the Title says) - how to efficiently
implement a scenario, where you have to manage "connectable, draggable Boxes"
(as in the Graph in the following screenshot):



And a video here:



There's a green highlighted Connection (with an appropriate ToolTip), which can - (especially
when the Path is complex) - often cause headaches with regards to: "how-to-implement".

With cairo we have two nice calls available, which can help a great deal, when solving
such more challenging "HitTest-problems":

- cCairoContext.InFill(x, y)
- cCairoContext.InStroke(x, y) <-- this one was used in the Demo

So, what one basically has to do to accomplish a complex HitTest is, to simply apply the Path
in question onto a CairoContext with the appropriate coordinates "as when truly rendered".

Even better, such a cairo-context doesn't have to be derived from "something physically"
(as e.g. a larger ImageSurface), a "virtual one" is already sufficient for that task.

For that purpose (when working with the WidgetEngine, as in this Demo) - each cWidgetBase
already offers such a context over W.MeasureContext.

A slight problem I found was, that whilst CC.InFill always worked reliably, CC.InStroke was only
delivering reliable Hits in 80-90% on the length of a complex Path (as e.g. the Beziers I used here,
due to rounding-errors in the cairo-C-Source).

Though I found a patch for that in the cairo-repo and backported that to the version (vb_cairo_sqlite.dll)
which comes with the RichClient - in consequence CC.InStroke will now work equally reliable as CC.InFill.

So the version of the RichClient (including the latest compile of vb_cairo_sqlite.dll) which will work
well with the zipped Demo-Archive below, needs to be at least 5.0.24 - please visit the Download-
page at vbRichClient.com and update your package appropriately before running it.


by
Olaf

Source:VBForums
Source: VBRichClient



Sunday, July 23, 2017

You just can't trust Microsoft anymore

We used VB6 and Microsoft abandoned it (though we are lucky that it still continues working, even on Windows 10 despite Microsoft). Microsoft behaved despicably with VB6 - always using phrases like "we have no plans to support VB6 in the next release of Windows". But they always had to because VB6 programming is so widely used.
We used Silverlight, it was very good but Microsoft abandoned that too.
We looked at LightSwitch, we liked it, we even used it a little. Fortunately we didn't do much with it because we could no longer trust Microsoft. And we were right not to trust MS because they abandoned that too.
Then we needed to develop mobile apps. But Microsoft could only offer us Windows Phone, which they kept breaking compatibility with (Windows Mobile 6, Windows Phone 7, Windows Phone 8) before losing out altogether.
You just can't trust Microsoft anymore.

Saturday, July 15, 2017

Get IP and MAC addres

Get IP and MAC addres


Private Sub Form_Load()

    Dim myWMI As Object, myObj As Object, Itm
    
    Set myWMI = GetObject("winmgmts:\\.\root\cimv2")
    Set myObj = myWMI.ExecQuery("SELECT * FROM " & _
                     "Win32_NetworkAdapterConfiguration " & _
                     "WHERE IPEnabled = True")
    For Each Itm In myObj
        MsgBox (Itm.IPAddress(0))
        MsgBox (Itm.MACAddress)
        Exit For
    Next

End Sub





Source: VBForums

Friday, July 7, 2017

They left because they lost all trust

David Sobeski was a General Manager with Microsoft. 
He posted about "what went wrong" https://www.facebook.com/dsobeski/posts/10153683440480008
"The trust with developers has been a long deteriorating problem. .... Then, everything went to **** when .NET was released. Changes were being made to the C language, to the Visual Basic language. In one fell swoop, Microsoft told all of its developers that everything they were doing and did was wrong. Stop all that crazy C code or the AddRef / Release or that insane VB or Access code and use the new new thing."
"Being a developer for a Microsoft platform was insane. Don't forget Office. One of the largest platforms on the planet. It avoided all this and you still used VBA. Office had to continue to use VBA because there was no guarantee of compatibility between VBA and VB.NET. But now you were an island."
"The Windows Phone team did something that would seal its fate forever and lose the trust of developers. Windows Phone 7 was released with a new user experience and was the answer to iOS and Android. It actually got developers excited. But, a year later with Windows Phone 8, Microsoft told all the developers that the investments they made in Windows Phone was a waste of time because none of their apps will work on Windows Phone 8. That was it. It was over."
Sobeski concludes: "At the end of the day, developers walked away from Microsoft not because they missed a platform paradigm shift. They left because they lost all trust. You wanted to go somewhere to have your code investments work and continue to work."
by Chucky1

Friday, June 9, 2017

Best Screen Recorder (VB6 source code)


Records the Full Screen or Screen "Window" Activity to an AVI video. Roberto Mior (aka reexre) wrote this code in a hurry. Roberto Mior is a brilliant Venetian programmer, a genius (without exaggeration) ! You should look for his projects online, if you want to see the most advanced technology and how is invented ! I had the honor of working with Roberto on neural networks regarding a very serious project (still underway). You can download the Visual Basic 6.0 source code below. You can see an example video here.

Download from me

Download from source







Sunday, June 4, 2017

Visual Basic 6.0 (Classic) upgrade to 7.0 should be able to compile standalone Win32, Win64 EXE and Android APK

1. First of all Visual Basic Classic should be brought back! (i.e: Visual Basic 7.0) 
2. Visual Basic Classic version should compile to standalone Win32, Win64 executables and Android applications (the APIs which are available and common to both).
By compiling to Android APK I mean the language of coding should be BASIC which is JAVA in Android Studio.
There are many programs/frameworks on the internet which use Basic Language to compile Android applications.
Even Delphi (Pascal) creates Android applications.
If Microsoft makes this new Visual Basic Classic, there will be a steep rise in Visual Basic Classic programmers. Any programmer on Earth will almost guarantee success for this idea.
Also if possible in later versions it should also be able to create Mac OS, Linux applications and Windows Mobile applications.
Microsoft should encourage this idea! I don't see any other better idea than this!
If Microsoft wouldn't have wasted time on .NET frameworks and thought of idea like this then Visual Basic Classic would have become the 1st choice to learn programming and also for making commercial applications.
Its time to make a good and wise decision before it is too late for Microsoft! Because .NET is not having a good future and many who migrated are opting out.

Microsoft have puublished a new Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008, Windows 7, Windows 8 and Windows 8.1, Windows Server 2012, Windows 10, and Windows Server 2016 ... 
https://docs.microsoft.com/en-us/dotnet/articles/visual-basic/reference/vb6-support
Microsoft have extended support of VB6 to Windows Server 2016. VB6 is supported until at least November 2027 on Windows Server 2016, and until at least 2025 on Windows 10. Both are likely to be extended.
VB6 programming is supported on Windows 10, Windows Server 2016 and earlier versions of Windows.
VBA programming is supported on Office 2016 and earlier versions of Office.
VBScript programming is still part of Windows.

Thursday, June 1, 2017

Visual Basic 6.0 is supported until at least November 2027

Microsoft have extended support of VB6 to include Windows Server 2016 as well as Windows 10. VB6 is supported until at least November 2027.
Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008, Windows 7, Windows 8 and Windows 8.1, Windows Server 2012, Windows 10, and Windows Server 2016 - Original page:
Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008, Windows 7, Windows 8 and Windows 8.1, Windows Server 2012, Windows 10, and Windows Server 2016
Update: March 2016

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 Vista
  • Windows Server 2008 including R2
  • Windows 7
  • Windows 8 and Windows 8.1
  • Windows Server 2012 including R2
  • Windows 10
  • Windows Server 2016
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 (http://support.microsoft.com/gp/lifepolicy). The support bar will be limited to serious regressions and critical security issues for existing applications.

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. However, Custom Support Agreements may be available from Microsoft. 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.dll was 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 (http://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 \Tools folder 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 http://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 http://www.microsoft.com/support.

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 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. Developers can think of the support story for Windows 7 as being the same as it is for Windows Vista.

Windows 8

Since the initial release of this support statement, the Windows 8 operating system has been released. This document has been updated to clarify Microsoft’s support for VB6 on Windows 8.
The VB6 runtime will ship and will be supported in Windows 8 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 as being the same as it is for Windows 7.

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 8.

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 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. Developers can think of the support story for Windows Server 2008 as being the same as it is for Windows Vista.

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 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 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 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.

Supported Windows operating system versions

This section provides additional information regarding the operating systems that offer some level of support for VB6.
Windows operating systemVB6 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 editionsYes *Yes *No, but Custom Support Agreements may be available.
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 editionsYes *Yes *No, but Custom Support Agreements may be available.
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 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 8, all 32-bit editionsYes *Yes *No, but Custom Support Agreements may be available.
Windows 8, 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 editionsYes *Yes *No, but Custom Support Agreements may be available.
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 Vista, all 32-bit editionsYes *Yes *No, but Custom Support Agreements may be available.
Windows Vista, 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 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 editionsYes *Yes *No, but Custom Support Agreements may be available.
Windows 2003 server, all 32-bit editions including R2Yes *Yes *No, but Custom Support Agreements may be available.
Windows 2003 server. all x64 editions including R2Yes *
32-bit apps running in WOW only
Yes *
32-bit apps running in WOW only
No
Note
* VB6 runtime support is limited by the OS support lifecycle. For example, if the target OS is in Extended support, VB6 cannot have a higher level of support than Extended support.

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 Vista, Windows Server 2008 including R2, Windows 7, Windows 8, Windows 8.1, Windows Server 2012 including R2, Windows 10, 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 Vista, Windows 7, Windows Server 2008, Windows 8, Windows 8.1, Windows Server 2012, Windows 10, and Windows Server 2016

Developers planning to use Visual Basic 6.0 with one of the listed Windows operating system 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 Windows Vista, Windows 7, Windows Server 2008, Windows 8, Windows 8.1, Windows Server 2012, Windows 10, or Windows Server 2016, please follow your normal support channels to report the issue.

Supported and shipping in Windows Vista, Windows 7, Windows Server 2008, Windows 8, Windows 8.1, Windows Server 2012, Windows 10, and Windows Server 2016

atl.dllmsadcor.dllmsorcl32.dllole2.dll
asycfilt.dllmsadcs.dllmsvbvm60.dllole32.dll
comcat.dllmsadds.dllmsvcirt.dlloleaut32.dll
compobj.dllmsaddsr.dllmsvcrt.dlloleaut32.dll
dbnmpntw.dllmsader15.dllmsvcrt40.dlloledb32.dll
dcomcnfg.exemsado15.dllmtxdm.dlloledb32r.dll
dllhost.exemsador15.dllmtxoci.dlloledlg.dll
ds16gt.dllmsadrh15.dllodbc16gt.dllolepro32.dll
ds32gt.dllmscpxl32.dllodbc32.dllolethk32.dll
expsrv.dllmsdadc.dllodbc32gt.dllregsvr32.exe
hh.exemsdaenum.dllodbcad32.exerpcns4.dll
hhctrl.ocxmsdaer.dllodbccp32.cplrpcrt4.dll
imagehlp.dllmsdaora.dllodbccp32.dllscrrun.dll
iprop.dllmsdaosp.dllodbccr32.dllsecur32.dll
itircl.dllmsdaprst.dllodbccu32.dllsimpdata.tlb
itss.dllmsdaps.dllodbcint.dllsqloledb.dll
mfc40.dllmsdasc.dllodbcji32.dllsqlsrv32.dll
mfc42.dllmsdasql.dllodbcjt32.dllstdole2.tlb
mfc42enu.dllmsdasqlr.dllodbctrac.dllstdole32.tlb
msadce.dllmsdatsrc.tlboddbse32.dllstorage.dll
msadcer.dllmsdatt.dllodexl32.dllvbajet32.dll
msadcf.dllmsdfmap.dllodfox32.dllvfpodbc.dll
msadcfr.dllmsdfmap.iniodpdx32.dll
msadco.dllmsjtes40.dllodtext32.dll

Supported runtime files to distribute with your application

comct232.ocxmsbind.dllmsdbrptr.dllmsstdfmt.dll
comct332.ocxmscdrun.dllmsflxgrd.ocxmsstkprp.dll
comctl32.ocxmschrt20.ocxmshflxgd.ocxmswcrun.dll
comdlg32.ocxmscomct2.ocxmshtmpgr.dllmswinsck.ocx
dbadapt.dllmscomctl.ocxmsinet.ocxpicclp32.ocx
dbgrid32.ocxmscomm32.ocxmsmapi32.ocxrichtx32.ocx
dblist32.ocxmsdatgrd.ocxmsmask32.ocxsysinfo.ocx
mci32.ocxmsdatlst.ocxmsrdc20.ocxtabctl32.ocx
msadodc.ocxmsdatrep.ocxmsrdo20.dll

Unsupported, but supported and compatible updates or upgrades are available

dao350.dllmsexch35.dllmsjter35.dllmsrepl35.dll
mdac_typ.exemsexcl35.dllmsjtor35.dllmstext35.dll
mschart.ocxmsjet35.dllmsltus35.dllmsxbse35.dll
msdaerr.dllmsjint35.dllmspdox35.dllodbctl32.dll
msdatl2.dllmsjt4jlt.dllmsrd2x35.dlloledb32x.dll

Unsupported runtime files

anibtn32.ocxspin32.ocxrpcltscm.dllrdocurs.dll
graph32.ocxgauge32.ocxrpcmqcl.dllvbar332.dll
keysta32.ocxgswdll32.dllrpcmqsvr.dllvisdata.exe
autmgr32.execiscnfg.exerpcss.exevsdbflex.srg
autprx32.dllolecnv32.dlldbmsshrn.dllthreed32.ocx
racmgr32.exerpcltc1.dlldbmssocn.dllMSWLess.ocx
racreg32.dllrpcltc5.dllwindbver.exetlbinf32.dll
grid32.ocxrpcltccm.dllmsderun.dlltriedit.dll
msoutl32.ocxrpclts5.dllodkob32.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

JPNKORCHTCHS
mfc42jpn.dllmfc42kor.dllmfc42cht.dllmfc42chs.dll
scrrnjp.dllscrrnko.dllscrrncht.dllscrrnchs.dll
vb6jp.dllvb6ko.dllvb6cht.dllvb6chs.dll
cmct2jp.dllcmct2ko.dllcmct2cht.dllcmct2chs.dll
cmct3jp.dllcmct3ko.dllcmct3cht.dllmscc2chs.dll
mscc2jp.dllmscc2ko.dllmscc2cht.dllcmct3chs.dll
cmctljp.dllcmctlko.dllcmctlcht.dllcmctlchs.dll
cmdlgjp.dllcmdlgko.dllmscmccht.dllmscmcchs.dll
mscmcjp.dllmscmcko.dllcmdlgcht.dllcmdlgchs.dll
dbgrdjp.dlldbgrdko.dlldbgrdcht.dlldbgrdchs.dll
dblstjp.dlldblstko.dlldblstcht.dlldblstchs.dll
mcijp.dllmciko.dllmcicht.dllmcichs.dll
msadnjp.dllmsadnko.dllmsadncht.dllmsadnchs.dll
adodcjp.dlladodcko.dlladodccht.dlladodcchs.dll
mschtjp.dllmschtko.dllmschtcht.dllmschtchs.dll
msch2jp.dllmsch2ko.dllmsch2cht.dllmsch2chs.dll
mscomjp.dllmscomko.dllmscomcht.dllmscomchs.dll
datgdjp.dlldatgdko.dlldatgdcht.dlldatgdchs.dll
datlsjp.dlldatlsko.dlldatlscht.dlldatlschs.dll
datrpjp.dlldatrpko.dlldatrpcht.dlldatrpchs.dll
dbrprjp.dlldbrprko.dlldbrprcht.dlldbrprchs.dll
flxgdjp.dllflxgdko.dllflxgdcht.dllflxgdchs.dll
mshfgjpn.dllmshfgkor.dllmshfgcht.dllmshfgchs.dll
htmprjp.dllhtmprko.dllhtmprcht.dllhtmprchs.dll
inetjp.dllinetko.dllinetcht.dllinetchs.dll
msmpijp.dllmsmpiko.dllmsmpicht.dllmsmpichs.dll
msmskjp.dllmsmskko.dllmsmskcht.dllmsmskchs.dll
rdc20jp.dllrdc20ko.dllrdc20cht.dllrdc20chs.dll
rdo20jp.dllrdo20ko.dllrdo20cht.dllrdo20chs.dll
stdftjp.dllstdftko.dllstdftcht.dllstdftchs.dll
mswcrjp.dllmswcrko.dllmswcrcht.dllmswcrchs.dll
winskjp.dllwinskko.dllwinskcht.dllwinskchs.dll
pcclpjp.dllpcclpko.dllpcclpcht.dllpcclpchs.dll
rchtxjp.dllrchtxko.dllrchtxcht.dllrchtxchs.dll
sysinjp.dllsysinko.dllsysincht.dllsysinchs.dll
tabctjp.dlltabctko.dlltabctcht.dlltabctchs.dll
ITAFRAESPDEU
mfc42ita.dllmfc42fra.dllmfc42esp.dllmfc42deu.dll
scrrnit.dllscrrnfr.dllscrrnes.dllscrrnde.dll
vb6it.dllvb6fr.dllvb6es.dllvb6de.dll
cmct2it.dllcmct2fr.dllcmct2es.dllcmct2de.dll
mscc2it.dllmscc2fr.dllmscc2es.dllmscc2de.dll
cmct3it.dllcmct3fr.dllcmct3es.dllcmct3de.dll
cmctlit.dllcmctlfr.dllcmctles.dllcmctlde.dll
mscmcit.dllmscmcfr.dllmscmces.dllmscmcde.dll
cmdlgit.dllcmdlgfr.dllcmdlges.dllcmdlgde.dll
dbgrdit.dlldbgrdfr.dlldbgrdes.dlldbgrdde.dll
dblstit.dlldblstfr.dlldblstes.dlldblstde.dll
mciit.dllmcifr.dllmcies.dllmcide.dll
msadnit.dllmsadnfr.dllmsadnes.dllmsadnde.dll
adodcit.dlladodcfr.dlladodces.dlladodcde.dll
mschtit.dllmschtfr.dllmschtes.dllmschtde.dll
msch2it.dllmsch2fr.dllmsch2es.dllmsch2de.dll
mscomit.dllmscomfr.dllmscomes.dllmscomde.dll
atgdit.dlldatgdfr.dlldatgdes.dlldatgdde.dll
datlsit.dlldatlsfr.dlldatlses.dlldatlsde.dll
datrpit.dlldatrpfr.dlldatrpes.dlldatrpde.dll
dbrprit.dlldbrprfr.dlldbrpres.dlldbrprde.dll
flxgdit.dllflxgdfr.dllflxgdes.dllflxgdde.dll
mshfgit.dllmshfgfr.dllmshfges.dllmshfgde.dll
htmprit.dllhtmprfr.dllhtmpres.dllhtmprde.dll
inetit.dllinetfr.dllinetes.dllinetde.dll
msmpiit.dllmsmpifr.dllmsmpies.dllmsmpide.dll
msmskit.dllmsmskfr.dllmsmskes.dllmsmskde.dll
rdc20it.dllrdc20fr.dllrdc20es.dllrdc20de.dll
rdo20it.dllrdo20fr.dllrdo20es.dllrdo20de.dll
stdftit.dllstdftfr.dllstdftes.dllstdftde.dll
mswcrit.dllmswcrfr.dllmswcres.dllmswcrde.dll
winskit.dllwinskfr.dllwinskes.dllwinskde.dll
pcclpit.dllpcclpfr.dllpcclpes.dllpcclpde.dll
rchtxit.dllrchtxfr.dllrchtxes.dllrchtxde.dll
sysinit.dllsysinfr.dllsysines.dllsysinde.dll
tabctit.dlltabctfr.dlltabctes.dlltabctde.dll