MSCAL.ocx - > CITRIX Metaframe XP

[Paul M]

Hi Peoples,

I'm having some problems with the mscal.ocx (Calendar Control Version 10.0)
and CITRIX clients.

THe problem is that I have the Calendar control on numerous forms where the
users is prompted to select a date for a report output.

The organisation has a standard SOE, however, with the CITRIX clients they
are encountering a runtime error as the reference to the control is to an
older version. From the information that I have been able to find the the KB
is that version 10.0 is not backward compitable with older versions of the
control.

All citrix clients have Office XP installed, however the calendar control
version is 8.0. I thought that this was a bit odd as the control v10.0 ships
with XP?

I have tried unregistering the control deleting the old file, saving the
correct (v10.0) file and re-registering the control via regsvr32. We have
tried registering it from both the [C:\WinNT\System32\] and the [C:\Program
Files\Microsoft Office\Office10] directories, with no luck. What I have
noticed is that on the Standard XP Pro machines, the control is listed (in
the reference list) as "Calendar Control Version 10.0" where when you
register it from the Office10 directory it lists as "Microsoft Calendar
Control Version 10.0". I'm not sure if tis means anything (by the name
change) but it won't allow the control to load.

Problems that are being encountered are:

The form control won't load, at all.

The form loads, and allows the user to press the date grid, but no event is
called (where there is a on_change event)

A run-time error crashes excel all together. (On module MSCAL.ocx) I'm sorry
I don't have the error number/address, I'll post it back tomorrow.

I guess what I'm asking is whether anyone else has had this sort of a
problem, and if so what options are there to get around it. Also, what is
the correct procedure to register the control via regsvr 32. I have been
told that in w2K you can register the control from the system32 directory,
without having the control in that directory, or is it BP to register it
from the Office10 dir, or register the control with the full path from the
system32 dir (ie. regsvr32 "C:\Program Files\Microsoft
Office\Office10\MSCAL.ocx"

Thanks in advance.

Paul M.

 

[Paul M]

After exhaustive testing and resolving to that the M$
Calendar Control needs a few more versions under it's
belt before M$ sort out the current issues. I have found
with thands to Phil From Dallsa, TX a coded Calendar for
use in an excel form. Doen't require the dredded
MSCAL.ocx and looks good to. See post on www.ozgrid.com

http://www.ozgrid.com/forum/viewthread.php?tid=891

to download the example file.

Paul M.

 

[keepitcool]

The book mentioned just uses the standard office calender control
distributed / installed with office (as an option under ms-access)

Works fine in Excel XP but completely crashed Excel 2003.

That was caused by the "poor" implement of getting it to load modeless
in xl97. Be very careful about the dragdrop statements and api stuff in
the book. They are all related to making the form modeless in Excel97
But the code is also (needlessly) run for newer versions.

When I disabled those lines and just loaded the form with vbmodeless
param I had no further probs.


form_activate
workbook_open
workbook_close


Can't test for Citrix though.

keepITcool

< email : keepitcool chello nl (with @ and .) >
< homepage: http://members.chello.nl/keepitcool >

After exhaustive testing and resolving to that the M$
Calendar Control needs a few more versions under it's
belt before M$ sort out the current issues. I have found
with thands to Phil From Dallsa, TX a coded Calendar for
use in an excel form. Doen't require the dredded
MSCAL.ocx and looks good to. See post on www.ozgrid.com

http://www.ozgrid.com/forum/viewthread.php?tid=891

to download the example file.

Paul M.

-----Original Message-----
Hi Peoples,

I'm having some problems with the mscal.ocx (Calendar Control Version 10.0)
and CITRIX clients.

THe problem is that I have the Calendar control on numerous forms where the
users is prompted to select a date for a report output.

The organisation has a standard SOE, however, with the CITRIX clients they
are encountering a runtime error as the reference to the control is to an
older version. From the information that I have been able to find the the KB
is that version 10.0 is not backward compitable with older versions of the
control.

All citrix clients have Office XP installed, however the calendar control
version is 8.0. I thought that this was a bit odd as the control v10.0 ships
with XP?

I have tried unregistering the control deleting the old file, saving the
correct (v10.0) file and re-registering the control via regsvr32. We have
tried registering it from both the [C:\WinNT\System32\] and the [C:\Program
Files\Microsoft Office\Office10] directories, with no luck. What I have
noticed is that on the Standard XP Pro machines, the control is listed (in
the reference list) as "Calendar Control Version 10.0" where when you
register it from the Office10 directory it lists as "Microsoft Calendar
Control Version 10.0". I'm not sure if tis means anything (by the name
change) but it won't allow the control to load.

Problems that are being encountered are:

The form control won't load, at all.

The form loads, and allows the user to press the date grid, but no event is
called (where there is a on_change event)

A run-time error crashes excel all together. (On module MSCAL.ocx) I'm sorry
I don't have the error number/address, I'll post it back tomorrow.

I guess what I'm asking is whether anyone else has had this sort of a
problem, and if so what options are there to get around it. Also, what is
the correct procedure to register the control via regsvr 32. I have been
told that in w2K you can register the control from the system32 directory,
without having the control in that directory, or is it BP to register it
from the Office10 dir, or register the control with the full path from the
system32 dir (ie. regsvr32 "C:\Program Files\Microsoft
Office\Office10\MSCAL.ocx"

Thanks in advance.

Paul M.


.