From: Peter T on
Which version of Mscomct2.ocx do you have, which contains the DTPicker. If
not 6.1.98.16 see here and install the latest

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

Regards,
Peter T

"Rick Rothstein" <rick.newsNO.SPAM(a)NO.SPAMverizon.net> wrote in message
news:OIZXGacyKHA.3408(a)TK2MSFTNGP06.phx.gbl...
>> I believe that file is in the Windows\System32 folder on an XP machine
>> (at
>> least it is on the XP Virtual Machine that I have on my W7-64 computer.
>
> Really? Do you have to do something to activate it? When I installed Vista
> on my computer a few months ago, (I could be wrong about this... old age
> and all<g>) I am almost positive that I looked to see if I could add the
> DatePicker control to a UserForm and couldn't until after I installed my
> copy of the compiler version of VB6.
>
> --
> Rick (MVP - Excel)


From: Ron Rosenfeld on
On Mon, 22 Mar 2010 19:22:20 -0000, "Peter T" <peter_t(a)discussions> wrote:

>Which version of Mscomct2.ocx do you have, which contains the DTPicker. If
>not 6.1.98.16 see here and install the latest
>
>http://support.microsoft.com/kb/957924
>
>Regards,
>Peter T

I have an older version of that file. OTOH, my OS is not listed in the
"applies to" portion of the MSKB article.
--ron
From: Peter T on
As you say, x64 is not included in the list of OS. I am surprised though,
AFAIK the VB6 runtime files are the same in 32 & 64 bit systems, although
not all of the files will work in x64, maybe that's why x64 is not listed.

However if your version of the control is older that might be the reason
it's not working, typically that's the explanation in other OS.

One thing though, I think most if not all those ActiveX controls will fail
to work in 64 bit Office, if that's what you have.

Regards,
Peter T

"Ron Rosenfeld" <ronrosenfeld(a)nospam.org> wrote in message
news:8hufq5tpfahil7gvdnjlnq8e3oo3rlpg2b(a)4ax.com...
> On Mon, 22 Mar 2010 19:22:20 -0000, "Peter T" <peter_t(a)discussions> wrote:
>
>>Which version of Mscomct2.ocx do you have, which contains the DTPicker. If
>>not 6.1.98.16 see here and install the latest
>>
>>http://support.microsoft.com/kb/957924
>>
>>Regards,
>>Peter T
>
> I have an older version of that file. OTOH, my OS is not listed in the
> "applies to" portion of the MSKB article.
> --ron


From: Ron Rosenfeld on
On Tue, 23 Mar 2010 09:09:07 -0000, "Peter T" <peter_t(a)discussions> wrote:

>As you say, x64 is not included in the list of OS. I am surprised though,
>AFAIK the VB6 runtime files are the same in 32 & 64 bit systems, although
>not all of the files will work in x64, maybe that's why x64 is not listed.
>
>However if your version of the control is older that might be the reason
>it's not working, typically that's the explanation in other OS.
>
>One thing though, I think most if not all those ActiveX controls will fail
>to work in 64 bit Office, if that's what you have.
>
>Regards,
>Peter T

My control *IS* older (6.00?) and *IS* working. I believe it was just in a
different directory on my W7-64 machine than on the XP-32 machine.
--ron
From: Peter T on
OK I misunderstood, I didn't realise the control is working. However, AFAIK,
the path of a registered control should not be relevant(though the VB
controls would normally be in the relevant system folder).

Regards,
Peter T

"Ron Rosenfeld" <ronrosenfeld(a)nospam.org> wrote in message
news:187hq5l79ehc1psab3net59j8utfmt94i8(a)4ax.com...
> On Tue, 23 Mar 2010 09:09:07 -0000, "Peter T" <peter_t(a)discussions> wrote:
>
>>As you say, x64 is not included in the list of OS. I am surprised though,
>>AFAIK the VB6 runtime files are the same in 32 & 64 bit systems, although
>>not all of the files will work in x64, maybe that's why x64 is not listed.
>>
>>However if your version of the control is older that might be the reason
>>it's not working, typically that's the explanation in other OS.
>>
>>One thing though, I think most if not all those ActiveX controls will fail
>>to work in 64 bit Office, if that's what you have.
>>
>>Regards,
>>Peter T
>
> My control *IS* older (6.00?) and *IS* working. I believe it was just in
> a
> different directory on my W7-64 machine than on the XP-32 machine.
> --ron