Re: Microsoft Calendar Control 11.0

[Nigel]

I guess you are using Excel 2003 or earlier? If so then the Calendar
Control v11 (mscal.ocx) was not supplied with the initial Excel
installation, and needs to be downloaded and installed on the target
machines. Excel 2007 has a version 12 loaded as standard.

Your simples option would be to remove the object from the UserForm, but you
probably will loose functionality. Consider downloading and installing the
calendar, reference here, but there are others..
http://www.fontstuff.com/mailbag/qvba01.htm

If you are using Excel 2007, then the calendar to reference is version 12
not version 11

--

Regards,
Nigel
nigel...@9sw.co.uk

"ryguy7272" <rygu...@discussions.microsoft.com> wrote in message
news:D5F8113A-4786-431D...@microsoft.com...
> Some people in my office recently (re)started using an Excel model that
> was
> used a long time ago. A guy who initially developed the model is not with
> the company anymore. Some people have experienced trouble inputting
> information into text boxes on the first UserForm that pops up (I
> personally
> never experienced this problem). On the machines where there is an error,
> I
> checked the VBA code and traced the problem to this: MISSING Microsoft
> Calendar Control 11.0. So, I unchecked the box next to the library, and
> then
> close the program and restart it and sometimes it works but sometimes it
> does
> not work. How can I permanently disable this Microsoft Calendar Control
> 11.0? Or, how can I prevent it from repeatedly coming up on certain
> machines
> in the office? I suspect there is a setting somewhere in Excel that would
> allow me to disable this feature.
>
> Regards,
> Ryan---
>
> --
> RyGuy

[ryguy7272]

Thanks for the look Nigel. Actually, there is no calendar on the UserForm.
That's why I'm baffled. I had a reference to Calendar Control 11.0 in my
Excel. I unchecked the box, asked a colleague to open the model from the
network, and it worked. Maybe this will resolve the issue; time will tell.
I wish I knew more about this... Does anyone know what may cause this
behavior. Do you think some employees may not be getting critical updates
for MSOffice?

Thanks again,
Ryan--

--
RyGuy

[Nigel]

That should resolve it. References will persist, even if you do not employ
them in your code, it is likely that the original developer set the
reference and did not reset it. If the object is referenced on a machine
with the mscal.ocx and it does not exist on the target machine or an out of
date version then you get the error you describe.

Critical updates for MSOffice is completely different, your IS department
should be controlling these.

--

Regards,
Nigel
nigel...@9sw.co.uk

"ryguy7272" <rygu...@discussions.microsoft.com> wrote in message

news:1B74D2EC-F17F-45D7...@microsoft.com...

[ryguy7272]

Thanks for letting me know about this!

Regards,