Hi,

can anyone tell me which is the latest VB6 Cumulative Update?
I mostly use common dialog and common control.

Common Controls Update - Nov-2005
http://support.microsoft.com/kb/896559

Dec-2008 (buggy)

May-2009
http://support.microsoft.com/kb/957924
http://www.microsoft.com/downloads/details.aspx?familyid=CB824E35-0403-45C4-9E41-459F0EB89E36&displaylang=en

Oct-2009
http://support.microsoft.com/kb/974899
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=974899

Which one should i use?

Thanks,
ab

http://mmm4vb6.atom5.com/security-update-woes-3184.html

*May-2009*
File name File version File size Date Time
Comctl32.ocx  6.0.98.16  614,992  3/24/2009 15:52

*Oct-2009*
File name File version File size Date Time
Comctl32.ocx  6.0.98.16  614,992  25-Sep-2009 01:32

No version change or filesize change but date is changed?

On Mon, 16 Aug 2010 23:30:11 +0530, "Abhishek"
<abhishek0***@hotmail.com> wrote:

Yep, it is a quandry, and you will be lucky to get a definitive
answer.

They have never been particularly good at listing what if any changes
or bug-fixes appear in which release/build. MS used to publish a "Dll
Database" which provided a list of all components and indicate what
Service Pack or Product they came with, but they have since
discontinued it.

In general, if offered a choice take the newest file date. But as you
have discovered this is no guarantee it will actually fix any
particular bug, bring anything new to the table, or won't in fact
cause some new problem.

One problem is Hot Fixes. These are components released to fix a
particular problem. You will often notice in the fine print that MS
usually recommends you don't install the Hot Fix unless you are
experiencing that specific problem, because the fix is seldom tested
against all products that might use it. That makes it tough to be
proactive.

The second is Security Patches. Even when known fixes are applied to
specific components MS may not go back and revise current Service
Pack/Products downloads.

Third and beyond problems ... a myriad of opportunities for adventure.
<g>

Rules of Thumb:
If given a choice download the latest 'n greatest in terms of date.
If experiencing a specific problem go online and search for a "hot
fix", submit a ticket to MS (if your still within the support window),
or simply roll-back.
If you are NOT experiencing any problems - don't be proactive, ie, "If
it ain't broke, don't fix it". <g>

-ralph

On Mon, 16 Aug 2010 14:02:34 -0500, ralph <nt_consultin***@yahoo.net>
wrote:

And it wasn't very reliable.    Many versions of various Access or Jet
specific DLLs were never put in there.

Tony

On Tue, 17 Aug 2010 18:59:00 -0600, Tony Toews
<tto***@telusplanet.net> wrote:

True. Which I always found particularily amazing since data access
components had to be, by far, the most common reason people queried
the database.

I asked about that at a MS show once. I was given some line about
those components being part of a 'suite', tied to a specific product,
and thus shouldn't be considered 'isolated' components. ???

Which we know is BS as there are plenty of other components that would
fall under that same classification which were published in detail.

But what can you say but - it's their stuff, they can do as they
please.

-ralph

Show quote Hide quote It doesn't matter. Your costumers may have any of the above. Get Virtual PC,
and apply each screw-up update and see how it affects your application.

Show quote Hide quote Lol! And much more to the point.

As a corollary to this sage advice; Every so often I run across a poor
hapless team with a leader who decides it would be a good idea to have
a complete and *detailed* inventory of all the components their
clients may be using with their application suite.

Even though the assignment is always handed off to the lowest on the
totem pole it is a always an expensive waste of time and mercifully
soon abandoned.

-ralph

Hotfix download link you requested

IMPORTANT INFORMATION

For your convenience, we put the hotfix that you requested on an HTTP site.
You can download the hotfix from this site without us filling up your e-mail
inbox.

WARNING   This hotfix has not undergone full testing. Therefore, it is
intended only for systems or computers that are experiencing the exact
problem that is described in the one or more Microsoft Knowledge Base
articles that are listed in "KB Article Numbers" field in the table at the
end of this e-mail message. If you are not sure whether any special
compatibility or installation issues are associated with this hotfix, we
encourage you to wait for the next service pack release. The service pack
will include a fully tested version of this fix. We understand that it can
be difficult to determine whether any compatibility or installation issues
are associated with a hotfix. If you want confirmation that this hotfix
addresses your specific problem, or if you want to confirm whether any
special compatibility or installation issues are associated with this
hotfix, support professionals in Customer Support Services can help you with
that. For information about how to contact support, copy the following link
and then past it into your Web browser:

   http://support.microsoft.com/contactus/

For additional support options, please copy the following link and then
paste it into your Web browser:

   http://support.microsoft.com/

Before you install this hotfix
------------------------------

If you decide to install this hotfix, please note the following items:

Do not deploy a hotfix in a production environment without first testing the
hotfix.

Back up the system or the computer that will receive the hotfix before you
install the hotfix.

Additional hotfix information
-----------------------------

This hotfix package uses a password. Therefore, you must enter for each
package the password that we included in this e-mail message. To make sure
that you enter the correct password, we recommend that you highlight, copy,
and then paste the password from this e-mail message when you are prompted.
If you do not enter the correct password, you cannot install the hotfix.

NOTE   Passwords are set to expire every seven days. Download the package
within the next seven days to make sure that you can extract the files. If
there are fewer than seven days left in the password change cycle when you
receive this e-mail message, you receive two passwords. If this is the case,
use the first password if you download the hotfix package before the date in
the "Password Changes On" field that is listed in the table at the end of
this e-mail message. Use the second password if you download the hotfix
package after the date in the "Password Changes On" field.

NOTE   For your convenience, we send the hotfix location to you in a
hyperlink. To connect to this hotfix location, you can click the hyperlink
in the "Location" field that is listed in the table at the end of this
e-mail message to have your Web browser open that location. However,
sometimes e-mail program settings disable hyperlinks. If the hyperlink in
this e-mail message is disabled, please copy the hyperlink in the "Location"
field and then past it into the address box of your Web browser. Make sure
that you include the exact text (without spaces) between the parentheses in
the http:// address.


Package:
-----------------------------------------------------------
-----------------------------------------------------------
KB Article Number(s): 974899
Language: English
Platform: i386
Location:
(http://hotfixv4.microsoft.com/Visual%20Basic%206.0/sp6/DevDiv766726/9818/free/397156_ENU_i386_zip.exe)
Password: Q9mUY5]ntW



NOTE   Make sure that you include all the text between "(" and ")" when you
visit this hotfix location.

On Mon, 16 Aug 2010 23:03:04 +0530, "Abhishek"
<abhishek0***@hotmail.com> wrote:

Don't use them.  Use the API calls instead if at all possible.  List
the controls you are using and folks can suggest alternatives.

Tony

I mostly use Common Dailog and Common Control, i am aware of some control
replacement like Common Control Repalcement Project, and code only solution
for Commong Dailog. i have used code only statusbar and common dailog in
some of my project but cant seems to find a good enough Toolbar and ListView
controls. here is a good site for unicode control but i havent tested them
yet www.timosoft-software.de



Show quoteHide quote

Abhishek schrieb:
Well, Timo's controls are recommandable!

Hi,

Abhishek schrieb:

Don't know if that helps, but I have compiled some infos, see below.

*****
* Overview
*****

KB896559 2005-11 Bugfix Update           : Superseeded

- Remark: Superseeded by KB957924, not longer necessary
- Files : Mscomctl.ocx, Comctl32.ocx only
- Fixes : Division by zero in mentioned files
- Bugs  : None

KB926857 2008-12 Security Update         : Superseeded

- Remark: Superseeded by KB957924, do not use!
- Bugs  : Many. Even MS does advice to not use it!

KB957924 2009-05 Cumulative update rollup: Mandatory

- Remark: Security update, with some other fixes too. Superseeds
KB896559 and
           KB926857, can be applied over both KB896559 and KB926857
- Files : Runtime extended files (selected ActiveX controls and libraries)
- Fixes : Security, stability, fixes especially for newer OSes (Vista
and up)
- Bugs  : Some say that it contains new bugs!

KB974899 2009-10 Hotfix for KB957924     : Not mandatory

- Remark: Hotfix, apply only if necessary
- Files : Same files as with KB957924 cumulative update rollup, only
Mswinsck
           control has changed (according to file list)!
- Fixes : Some bugs introduced with KB957924
- Bugs  : Some say that it did not fix all bugs introduced with KB957924!

Situation is still unclear. KB896559 works. KB926857 is superseeded by
KB957924,
because KB926857 introduced many bugs. KB926857 still has bugs, some of them
being adressed in KB974899. However some people say that KB974899 dos not
resolve other bugs introduced in KB957924! Sadly no one says what bugs!


*****
* KB896559 2005-11 Bugfix Update
* Mscomctl.ocx, Comctl32.ocx
*****

http://support.microsoft.com/kb/896559

FIX: The Windows Common Controls Mscomctl.ocx or Comctl32.ocx may cause your
application or the Visual Basic 6 IDE to unexpectedly quit, or you may
receive a
"Divide By Zero" error message


*****
* KB926857 2008-12 Security Update
* Runtime Extended Files (some ActiveX Controls)
*****

http://support.microsoft.com/kb/926857/

This update introduced many new bugs! Do not use! Even MS (see below)
recommends
to not use it. Is completely replaced by KB957924 (see below).

MS08-070: Description of the security update for Microsoft Visual Basic 6.0
Service Pack 6 Runtime Extended Files: December 9, 2008

Microsoft has released cumulative update 957924 for the Microsoft Visual
Basic
6.0 Service Pack 6 (SP6) Runtime Extended Files. This cumulative update
contains
all the fixes in security update 926857 and includes several other stability
fixes and performance fixes for the ActiveX controls that are included
in the
Visual Basic 6.0 Runtime Extended Files. Additionally, the ActiveX
controls that
are included in this cumulative update will be the baseline for any future
updates for these ActiveX controls. This includes security updates and
hotfixes
for these ActiveX controls. Therefore, we strongly recommend that you
install
cumulative update 957924 to have the latest supported baseline for these
ActiveX controls.


*****
* KB957924 2009-05 Cumulative update rollup
* Runtime Extended Files (selected ActiveX controls and libraries)
*****

http://support.microsoft.com/kb/957924

Description of the cumulative update rollup for the Visual Basic 6.0 Service
Pack 6 Runtime Extended Files

Microsoft has released a cumulative update rollup for the Microsoft
Visual Basic
6.0 Service Pack 6 (SP6) Runtime Extended Files. This cumulative update
rollup
includes security update 926857 and updated versions of many other Microsoft
ActiveX controls that make up the Visual Basic 6.0 Runtime Extended Files.

* What are the Visual Basic 6.0 Runtime Extended Files?

The Visual Basic 6.0 Runtime Extended Files include select ActiveX
control OCX
files, libraries, and tools that are delivered together with the Visual
Basic
6.0 IDE media and as an online release. Typically, the Visual Basic 6.0
IDE or
the Microsoft.com Web site installs these files on the development system.
Then, the developer redistributes these files together with the developer's
applications.

* Do I really need this cumulative update rollup?

Yes. This cumulative update rollup contains the previously mentioned
security
fixes and several other stability fixes and performance fixes for the
ActiveX
controls that are included in the Visual Basic 6.0 Runtime Extended Files.
Additionally, the ActiveX controls that are included in this cumulative
update
rollup will be the baseline for any future updates for these ActiveX
controls.
This includes security updates and hotfixes for these ActiveX controls.
Therefore, we strongly recommend that you install this cumulative update
rollup to have the latest supported baseline for these ActiveX controls.

* I am a third-party software developer, and I use the ActiveX controls
in my
   application. What do I have to do?

If you redistribute the ActiveX controls, make sure that you update the
version of the ActiveX controls that are installed together with your
application by downloading this cumulative update rollup.

* I am developing software that contains a redistributable ActiveX control.
   What do I do?

Install this cumulative update rollup for your development software. If you
redistributed an ActiveX control together with an application, issue an
updated version of the application to your customers. In the updated version
of the application, include the updated version of the file in this
cumulative
update rollup for your development software.


*****
* KB974899 2009-10 Hotfix for KB957924
* Runtime Extended Files (selected ActiveX controls and libraries)
* Same files as with KB957924 cumulative update rollup
*****

http://support.microsoft.com/kb/974899
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=974899

This seems to just fix some specific problems. MS advices to not apply this
hot fix if the problem does not occur on your computer. Additionally the hot
fix includes all the files from the KB957924 cumulative update rollup, with
only the file Mswinsck.ocx changed (version and file size), all other files
staying unchanged!

* Symptoms

Consider the following scenario:

* You have installed Microsoft Visual Basic 6.0 Service Pack 6 (SP6) on a
   computer.

* You install the security update MS08-070 that is described in Microsoft
   Knowledge Base (KB) article 926857, or you install the Visual Basic 6.0
   cumulative update rollup that is described in KB article 957924.

* You use a version of the Microsoft Winsock control (mswinsck.ocx). The
   version number of the control is between 6.01.9812 and 6.01.9816.

* You have a Visual Basic application that contains an ImageList
control. The
   control contains a ListImage object that uses an IPicture interface.

In this scenario, you run the application, and then you receive the
following
error message:

Error 481: Invalid Picture.

* Resolution

A supported hotfix is available from Microsoft. However, this hotfix is
intended to correct only the problem that is described in this article.
Apply
this hotfix only to systems that are experiencing this specific problem.

Thanks for the Info :)

Check this out, its strange

KB-896559 (Nov-2005)
Size of comctl32.ocx is increase to 1.28 MB

KB-957924 (May-2009)
size of comctl32.ocx is decrased to 600 KB


anyway, its seems May-2009 is the stable update, i will apply that.

Hi,

Abhishek schrieb:

I would not worry about that.
But please remember: there *are* issues with this update! Sadly there is
no list (from MS or from the web), that specifies the issues.

So what do *Most* people do?

Apply the most recent stable update or use SP6 controls?

I used the 2005 Update only until today, when I installed the 2009-03
update (with fingers crossed :-)).

In the german newsgroups there were reports on errors, which might be
traced back to the 2009-03 update. I do not know, how many people use
the 2009-03 update. Obviously some do.

I have made a blog where I would be posting info about VB6 tools, updates,
fixes, controls etc anything to make VB6 usable for few more years.
http://vb6zone.blogspot.com (still under construction)


Show quoteHide quote

Abhishek schrieb:
Went to the bookmarks :-)

Thx. you can also submit anything useful you may find.


Show quoteHide quote

I was quite interested in the ThunderVB thing on your site that allows you
to include ASM in VB code. When I first got into computers one of my very
first languages was Oric Basic, and within a month or so my second language
(if you can call it that) was 6502 machine code (later supplemented by a
simple ASM that I had written myself in Oric Basic because I did not know
whether one already existed and in any case I could not afford to buy one
even if it did!). I really loved machine code (although in those days it was
very much simpler of course, with just 252 machine code instructions on the
6502 as I recall), and if I were a younger man then I would definitely take
it up again on the PC, despite the obviously massive leap in processor
architecture, and it would be nice to incorporate it into VB using the
ThunderVB stuff. I probably will not do that now at my age, but I really
liked your object of extending the life of VB6 and, although I have not yet
looked at your site in detail, I applaud you for it.

Mike

Backup of control is created by the setup here.

Microsoft Visual Studio\Common\Tools\VB\Controls\Controls_Backup


Show quoteHide quote

Hi,

test schrieb:
I know, but that doesn't help much, because MS writes that this update
could not be redone. So MS does not provide the means to convienently
undo the update. I would have to do it by hand, not knowing what exactly
the update changed (beside the obviously changed files copied).

On Thu, 19 Aug 2010 00:09:30 +0530, "Abhishek"
<abhishek0***@hotmail.com> wrote:

I'm not most people.  But within VB6 and Access I do my absolute best
to avoid using controls.    If that means my app doesn't look as fancy
or glittery oh well.

Tony

On 18/08/2010 19:39, Abhishek wrote:
I distribute the SP6 controls so they have AT LEAST those versions.
I leave further updates to their Windows Update.
If they already have newer versions, I don't touch them.

That's exactly the way it should be done.  Would you believe there are still
apps that force the original VB6 runtimes on the sys folder, using the P&D
wizard?

Are VB6 Controls also updated by Windows Updates?


Show quoteHide quote

On Thu, 26 Aug 2010 12:42:54 +0530, "Abhishek"
<abhishek0***@hotmail.com> wrote:

Depends on what you mean by "Windows Updates", to a degree what you
mean by "updated", and also on the version of Windows and MS products
being used.

And I'm only half-joking. Any typical client or home box, especially
with a preponderance of MS, speciality applications, and shareware
products will over time show a change (in terms of builds and file
dates) in these components. How and when they got there - no one ever
seems to know. <bg>

-ralph

i recently reinstalled windows, so had to reinstalle VB6 with sp6. my
automatic updates are turned on with all updates applied but i cant seems to
find the change in any of the VB6 OCX files. they are same as of sp6. and i
wont use the windows update on website just the desktop one.



Show quoteHide quote

On Fri, 27 Aug 2010 00:38:28 +0530, "Abhishek"
<abhishek0***@hotmail.com> wrote:

It would appear then, that the "Windows Update" does not touch any VB6
OCXs, and you have answered your own question.

-ralph

Show quote Hide quote That really only means that the updates HE applied apparently did not update
any VB6 OCXs.

Show quote Hide quote Shhhhh!

He is probably happy with his discovery, so let it be.

-ralph
<g>

yea, i am happy. so let it be. only if you have read my post before replying

"i recently reinstalled windows, so had to reinstalle VB6 with sp6. my
*automatic updates are turned on with all updates applied* but i cant seems
to find the change in any of the VB6 OCX files."


Show quoteHide quote

At least some are, which are considered a security update, rather than a VB6
files update. You can see the list of files in the articles themselves.

GDI+ and resizing a PictureBox
KBasic
.NUT Fail
Microsoft may back off of .NET languages
ActiveX EXE SingleUse Vs MultiUse
DCOM Error
.Net slipped itself in while I wasn't looking!
Specify DLL version when using mc.exe, rc.exe and/or link.exe
Formating Hex Values
MsgBox and a pop up form