Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
The same mscal.ocx working on Windows NT is not working on Windows XP.The file on both the OS are exactly identical (Version 8.0.0.5007). When this control used in an VB application gives automation error in runtime on Windows XP. While the same application works fine on Windows NT.

I face the same problem and to be more
focused:
1. the month property returns 16
2. the year property is causes r.t.e.
4. attempt to see the properties of the control in VB6 causes crash of the whole IDEAny way to overcome the problem will be appreciated.

Greg and Others
Sorry!! I never came back on forum to see what Response there was as I sorted it later that day.
The problem is a bugged version of MSCal.ocx that originates in Office XP (Probably Access) NOT Windows XP per se.
The work around is to dergister MScal.ocx overwrite with the old version and re register.
MSCal.ocx v 9.0.0.2607 which I am using is def OK
V 10.0.0.2601? is NOT
Use Regsvr32/u mascal.ocx
then
Regsvr32 c:\......\mascal.ocx
There are several bug reports from various vendors detailing this and a report from Ms themselves (which appears misleading in that it implies that the problem does not apply to VB..... and it does.)
Hope this helps
Best wishes
Martin
Martin Young
Smith & Young Sales Ltd
Marketers of MaxForms
Addon software for Maximizer CRM software
The White House
Toys Hill
Westerham
Kent TN16 1QG
England
Email: martin@saysales.com
Website: www.saysales.com
Telephone:+44 (0) 1732 750364
Fax: +44 (0) 1732 750899
(omit the (0) from overseas

Hi
I worked around that problem in Access of XP:
- form's "old" calender control (object) deleted
- new Calenter Control 10.0 were addedAfter that my "calender form" works nicely!
The version of MSCAL.OCX is 10.0.0.2601.
Wth rgdsMatti Purojarvi
Lahti, Finland

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |