What .OCX should be included to use ffc_olecalendar?  
Author Message
mikesteven





PostPosted: Mon Dec 15 14:32:32 CST 2003 Top

Exchange Servers >> What .OCX should be included to use ffc_olecalendar?

Hi all,

I've just delivered an apps that utilize ffc_olecalendar today, but I
found that my apps cannot find the .ocx on the target machine (P2-400
under Win98SE 128MB). Problem was, I forgot to put the merge file in the
installation set. A bit panic (in front of my client -- imagine that, I
had to stay cool!), I recreated the installation set on my laptop and
included _all_possible_ common control merge modules in the
InstallShield (MSCOMCTL.MSM, MSCOMCT2.MSM, MSCOMCT332.MSM). Of course it
worked (and I managed to save my face <lol>), but I'm still wondering
which one does the trick? I currently don't have a 'clean machine' to
test with. Just sold my Duron 1GHz.

TIA,
Willianto
P.S: I use VFP8SP1 (and VFP7SP1 occasionally).

Exchange Server35  
 
 
Leemi





PostPosted: Mon Dec 15 14:32:32 CST 2003 Top

Exchange Servers >> What .OCX should be included to use ffc_olecalendar? Hi Willianto:

I believe the OleCalenday FFC uses the monthview control that is in
MSCOMCT2.OCX. The merge module is mscomct2.msm (Microsoft Common Controls-2
6.0).

I hope this helps.

This posting is provided "AS IS" with no warranties, and confers no rights.

Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell

*-- VFP8 HAS ARRIVED!! --*
Read about all the new features of VFP8 here:
http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
Purchase VFP8 here:
http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518

Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retires Sept. 30th, 2003


>Hi all,

>I've just delivered an apps that utilize ffc_olecalendar today, but I
>found that my apps cannot find the .ocx on the target machine (P2-400
>under Win98SE 128MB). Problem was, I forgot to put the merge file in the
>installation set. A bit panic (in front of my client -- imagine that, I
>had to stay cool!), I recreated the installation set on my laptop and
>included _all_possible_ common control merge modules in the
>InstallShield (MSCOMCTL.MSM, MSCOMCT2.MSM, MSCOMCT332.MSM). Of course it
>worked (and I managed to save my face <lol>), but I'm still wondering
>which one does the trick? I currently don't have a 'clean machine' to
>test with. Just sold my Duron 1GHz.

TIA,
>Willianto
>P.S: I use VFP8SP1 (and VFP7SP1 occasionally).

 
 
Rick





PostPosted: Tue Dec 16 09:23:24 CST 2003 Top

Exchange Servers >> What .OCX should be included to use ffc_olecalendar? Willianto,
In the help file go to the topic "ActiveX Controls Overview" - it lists =
the file names of the OCXs and the help (CHM) files for the included MS =
ActiveX controls.

Rick



> Hi all,
>=20
> I've just delivered an apps that utilize ffc_olecalendar today, but I
> found that my apps cannot find the .ocx on the target machine (P2-400
> under Win98SE 128MB). Problem was, I forgot to put the merge file in =
the
> installation set. A bit panic (in front of my client -- imagine that, =
I
> had to stay cool!), I recreated the installation set on my laptop and
> included _all_possible_ common control merge modules in the
> InstallShield (MSCOMCTL.MSM, MSCOMCT2.MSM, MSCOMCT332.MSM). Of course =
it
> worked (and I managed to save my face <lol>), but I'm still wondering
> which one does the trick? I currently don't have a 'clean machine' to
> test with. Just sold my Duron 1GHz.
>=20
> TIA,
> Willianto
> P.S: I use VFP8SP1 (and VFP7SP1 occasionally).
>=20
>
 
 
Willianto





PostPosted: Wed Dec 17 08:49:19 CST 2003 Top

Exchange Servers >> What .OCX should be included to use ffc_olecalendar? Lee,
Thanks for your confirming that.

WBR,
Willianto


> Hi Willianto:
>
> I believe the OleCalenday FFC uses the monthview control that is in
> MSCOMCT2.OCX. The merge module is mscomct2.msm (Microsoft Common
> Controls-2
> 6.0).
>
> I hope this helps.
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> Sincerely,
> Microsoft FoxPro Technical Support
> Lee Mitchell
>
> *-- VFP8 HAS ARRIVED!! --*
> Read about all the new features of VFP8 here:
> http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
> Purchase VFP8 here:
> http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518
>
> Keep an eye on the product lifecycle for Visual FoxPro here:
> http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
> - VFP5 Mainstream Support retired June 30th, 2003
> - VFP6 Mainstream Support retires Sept. 30th, 2003
>
>
>> Hi all,
>
>> I've just delivered an apps that utilize ffc_olecalendar today, but I
>> found that my apps cannot find the .ocx on the target machine (P2-400
>> under Win98SE 128MB). Problem was, I forgot to put the merge file in
>> the installation set. A bit panic (in front of my client -- imagine
>> that, I had to stay cool!), I recreated the installation set on my
>> laptop and included _all_possible_ common control merge modules in
>> the InstallShield (MSCOMCTL.MSM, MSCOMCT2.MSM, MSCOMCT332.MSM). Of
>> course it worked (and I managed to save my face <lol>), but I'm
>> still wondering which one does the trick? I currently don't have a
>> 'clean machine' to test with. Just sold my Duron 1GHz.
>
> TIA,
>> Willianto
>> P.S: I use VFP8SP1 (and VFP7SP1 occasionally).


 
 
Willianto





PostPosted: Wed Dec 17 08:48:29 CST 2003 Top

Exchange Servers >> What .OCX should be included to use ffc_olecalendar? Rick,
Thanks for your directing me to the article.

WBR,
Willianto


> Willianto,
> In the help file go to the topic "ActiveX Controls Overview" - it
> lists the file names of the OCXs and the help (CHM) files for the
> included MS ActiveX controls.
>
> Rick
>


>> Hi all,
>>
>> I've just delivered an apps that utilize ffc_olecalendar today, but I
>> found that my apps cannot find the .ocx on the target machine (P2-400
>> under Win98SE 128MB). Problem was, I forgot to put the merge file in
>> the installation set. A bit panic (in front of my client -- imagine
>> that, I had to stay cool!), I recreated the installation set on my
>> laptop and included _all_possible_ common control merge modules in
>> the InstallShield (MSCOMCTL.MSM, MSCOMCT2.MSM, MSCOMCT332.MSM). Of
>> course it worked (and I managed to save my face <lol>), but I'm
>> still wondering which one does the trick? I currently don't have a
>> 'clean machine' to test with. Just sold my Duron 1GHz.
>>
>> TIA,
>> Willianto
>> P.S: I use VFP8SP1 (and VFP7SP1 occasionally).