> Thanks to the people who responded to my previous query. I've now tracked
> down the problem to an incompatibility in versions of comctl32.ocx.
> http://www.gridlinx.com/annoy.htm gives the solution of downloading a
patch
> from http://msdn.microsoft.com/vbasic/downloads/axupgrade.asp which
upgrades
> any project that uses comctl32.ocx to using MSCOMCTL.OCX instead.

> Problem - the patch doesn't run unless one has VB6 installed, which I
don't
> have, nor do I want it (because of the lousy help system). Would it be OK
to
> bundle my version of comctl32.ocx with the project setup, or would that
just
> cause more problems?

> --
> Roger Musson

>> Thanks to the people who responded to my previous query. I've now tracked
>> down the problem to an incompatibility in versions of comctl32.ocx.
>> http://www.gridlinx.com/annoy.htm gives the solution of downloading a
>patch
>> from http://msdn.microsoft.com/vbasic/downloads/axupgrade.asp which
>upgrades
>> any project that uses comctl32.ocx to using MSCOMCTL.OCX instead.

>> Problem - the patch doesn't run unless one has VB6 installed, which I
>don't
>> have, nor do I want it (because of the lousy help system). Would it be OK
>to
>> bundle my version of comctl32.ocx with the project setup, or would that
>just
>> cause more problems?

>> --
>> Roger Musson

>Read on:

>FILE: VBRun60.exe Installs Visual Basic 6.0 Run-Time Files
>VBRun60.exe is a self-extracting executable file that installs the
Microsoft
>Visual Basic run-time files that all applications created with Visual Basic
>6.0 need in order to run.
>* http://support.microsoft.com/support/kb/articles/q192/4/61.asp
>--

>Henri Leboeuf
>Web page: http://www.generation.net/~hleboeuf/index.htm