Missing Calendar Control

[Paul3rd]

Hello,
After converting Office 2000 to 2003 I've lost the Calendar Control 11.0.
It is no longer in the toolbox or when I go to Access - Tools - ActiveX
Controls to register it, it is not there either. MSCAL.OCX exists in my
System 32 folder and in the Microsoft Office - Office 11 folder.
How do I get the control back?
Or reinstall it?
Thanks for any help,
Paul

 

[Paul3rd]

Sorry! Never Mind,
I found the problem 10 minutes after I posted.
Paul

 

[Larry Daugherty]

Hi Paul,

The idea is that once you find the solution to a problem that you've
posted you should also post the solution - even if it's an "Oopsie"
and possibly embarrassing. There may have been hundreds of people
lurking who would like to not only that you have solved your problem
but also what the solution was.

HTH

 

[Gdareos]

I agree! I inherited an Access '97 application at work, and I can't
find the Calendar control either. I've got it in my home's Access
2007, but that doesn't help.

Thanks, Larry

 

[Douglas J. Steele]

In versions of Access prior to Access 2007, you're far better off not using
the calendar control. Take a look at what Jeff Conrad has at
http://www.accessmvp.com/JConrad/accessjunkie/calendars.html for far better
approaches.

 

[Evi]

in Form Design, click on More Controls button (looks like a hammer)

Note that this control doesn't have an On Click Event in its Properties but
if you open up a code page, choose the control (named by default ActiveXCT)
using the top left drop down box and choose OnClick using the top right drop
down you can put your code there.
Evi

 

[Evi]

You are being uncharacteristically hard Doug
The calendar control in Acc97 is certainly quirky (no On Click event in
Properties and looks dreadful if you make it smaller than 6.5 * 3.5cm ) but
it seems to work OK when I've used it. What problems are users encountering
with it?

Evi

 

[Douglas J. Steele]

The Calendar Control (like most other controls) is subject to versioning
problems. If you develop an application and you have, say, version
8.0.0.3432 of mscal.ocx on your machine and you then copy it to a machine
which has version 8.0.0.3218 of mscal.ocx on it, you may very find that
nothing in the application works anymore (the classic "Missing Reference"
problem). It's the same reason why most of use recommend using the
GetOpenFileName API (as illustrated in
http://www.mvps.org/access/api/api0001.htm at "The Access Web") rather than
the Common Dialog control.

A general rule of thumb is to avoid ActiveX controls as much as you can:
make the References collection as small as you can get away with. The
all-API calendar that Stephen Lebans has at
http://www.lebans.com/monthcalendar.htm is far, far more reliable, as are
the all-Access solutions mentioned in many of Jeff's other references.

 

[Evi]

Thanks Douglas. I'll remember that.
Evi

The Calendar Control (like most other controls) is subject to versioning
problems. If you develop an application and you have, say, version
8.0.0.3432 of mscal.ocx on your machine and you then copy it to a machine
which has version 8.0.0.3218 of mscal.ocx on it, you may very find that
nothing in the application works anymore (the classic "Missing Reference"
problem). It's the same reason why most of use recommend using the
GetOpenFileName API (as illustrated in
http://www.mvps.org/access/api/api0001.htm at "The Access Web") rather than
the Common Dialog control.

A general rule of thumb is to avoid ActiveX controls as much as you can:
make the References collection as small as you can get away with. The
all-API calendar that Stephen Lebans has at
http://www.lebans.com/monthcalendar.htm is far, far more reliable, as are
the all-Access solutions mentioned in many of Jeff's other references.