MSCAL (Calendar Control) causing a run-time error

[Kevin Williamson]

Keith,

When you are displaying the control are you doing any type of
initialization (ie. Calendar1.Value = Now)? If so, is this error occurring
on any particular line of code? What is the version number that you are
distributing? Does the same thing happen if you have a program that just
has a Calendar control on the main form and no code behind it?

Kevin Williamson - Microsoft Visual Basic Developer Support
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.

--------------------
| From: "Keith Kovala" <kov...@oz-online.net>
| Subject: MSCAL (Calendar Control) causing a run-time error
| Date: Wed, 21 Nov 2001 19:16:09 -0600
| Lines: 17
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 5.50.4522.1200
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
| Message-ID: <ucw9ZOvcBHA.1552@tkmsftngp02>
| Newsgroups: microsoft.public.vb.controls
| NNTP-Posting-Host: wks-65-27-97-119.kscable.com 65.27.97.119
| Path: cppssbbsa01.microsoft.com!tkmsftngp01!tkmsftngp02
| Xref: cppssbbsa01.microsoft.com microsoft.public.vb.controls:121136
| X-Tomcat-NG: microsoft.public.vb.controls
|
| I've got an application that makes use of the Calendar control from MSCAL
in
| several places, and it works fine on both my computers, and a couple
others
| the application hs been installed on, but on one particular one it keeps
| causing a run-time error. The error is 2147352560(80020010) and
| 2147417848(80010108) and the only information that seems to be available
| abou this is an automation error being used with a client server type
| setup... and I'm doing nothing of the sort.... I get these errors as soon
as
| the tab or form that has a calendar control on it is opened..... anyone
else
| seen this?! Any ideas?! The ocx file has the same size and time date
| stamp on all instances of installation, so it's not like it's the wrong
| version of the file... incidently the file is dated 2 February 2001, and
| 112KB. Version 10 I beleive.
|
| Any suggestions would be appreciated.
| Keith
|
|
|

[Keith Kovala]

Yes there is initailization code, at one location the Calendar.Value is set
to the current date, then at the other the Calendar.Value is set to a date
30 days from the current date. Unable to tell if it's the initialization
line of code because the computer having the problem is 600 miles away and
running a copy of the deployed application and no debugging tools are
present there to further troubleshoot. Though I have narrowed it done to
the MSCAL control or something related to it because the error occurs at two
distinct locations in the program only when trying to display a calendar
control. The three things on the form in one location is the calendar and a
label saying "Due date is set to " & Calendar.Value and a "close" cmdbutton
to dismiss the form. According to the components list for the project I'm
using Microsoft Calendar Control 10.0. As far as checking to see if the
computer will display a calendar control without any intialization code, if
I end up going to do some on site troubleshooting I'll use that to further
diagnose.

Keith

"Kevin Williamson" <kwill...@microsoft.com> wrote in message
news:liyMydr...@cppssbbsa01.microsoft.com...

[Keith Kovala]

Also, have been further told that it reads "Automation Error" but none of
the stuff I can find on "automation Error" seems to fit. They are using
Windows98, so that knocks out all the site server and WindowsNT stuff, but I
can't seem to nail this down. Now have a second computer exhibiting the
same problem. SO this might help in narrowing things down. Also, thought I
should mention, I am using VB v6.0 sp5.

"Kevin Williamson" <kwill...@microsoft.com> wrote in message
news:liyMydr...@cppssbbsa01.microsoft.com...

[Keith Kovala]

Kevin,

I have some breaking information that may further narrow down the problem
and would like to get this up and running as soon as possible, I know,
doesn't everyone. Anyways, as posted there is now a second computer
exhibiting this problem, but I was able to get further information this
time, the Calendar is being displayed but the run-time error happens before
the screen/form is fully loaded, in fact the date showing on the calendar is
October 27, 2001, which is the date set my the control as that was the date
I placed it on the form, so the new value of the calendar may well be the
problem, I'm using Calendar1.Value = DateTime.Date to set the date. Could
this well be the problem? Is there a better way to set it to the current
date, and what about the one where it's displaying today's date + 30?! There
I have an conditional checking to see if the date was passed and if so
Calendar1.Value = vNewValue else it goes to Calendar1.Value = DateTime.Date
like previously.

I do appreciate all your time and assistance in this.

Keith

"Kevin Williamson" <kwill...@microsoft.com> wrote in message
news:liyMydr...@cppssbbsa01.microsoft.com...

[Kevin Williamson]

Keith,

The first thing I would do is make sure the control is registered properly
by doing regsvr32 mscal.ocx. I am assuming it is since you are seeing the
control, but this is a quick and easy step just to make sure.

You will be getting this runtime error on a specific line of code in your
application so you could add some debugging code (ie. file logging or
messages to the user) to narrow down exactly which line of code it is. I
believe it will be a line like Calendar1.Value = DateTime.Date. Change
this to Calendar1.Value = Str(DateTime.Date).

If this doesn't solve it please let me know what line you find is causing
the problem.

Kevin Williamson - Microsoft Visual Basic Developer Support
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.

--------------------
| From: "Keith Kovala" <kov...@oz-online.net>

| References: <ucw9ZOvcBHA.1552@tkmsftngp02>
<liyMydr...@cppssbbsa01.microsoft.com>
| Subject: Re: MSCAL (Calendar Control) causing a run-time error
| Date: Tue, 27 Nov 2001 13:35:59 -0600
| Lines: 83

| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 5.50.4522.1200
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200

| Message-ID: <#tJEVs3dBHA.1456@tkmsftngp04>

| Newsgroups: microsoft.public.vb.controls
| NNTP-Posting-Host: wks-65-27-97-119.kscable.com 65.27.97.119

| Path: cppssbbsa01.microsoft.com!tkmsftngp01!tkmsftngp04
| Xref: cppssbbsa01.microsoft.com microsoft.public.vb.controls:121416
| X-Tomcat-NG: microsoft.public.vb.controls

[Keith Kovala]

Problem solved.

I had already mad sure the control was registered, but what I did was
unregister it, and then reinstalled the app, works like a charm. Found out
the error is caused my overwriting an existing mscal.ocx file without
registering instead of getting rid of the old and puttin gin the new. So my
question is now, how do I get this accomplished in PDW?

Thanks, Kevin, you've been great help!

"Kevin Williamson" <kwill...@microsoft.com> wrote in message

news:K7A7mNE...@cppssbbsa01.microsoft.com...

[Kevin Williamson]

The PDW will automatically uninstall an old version of a file and reinstall
and register a new version of a file. You can't, and you would never want
to, overwrite a newer version of a file with an older version. If you are
noticing that the problem is occurring with a newer version of mscal.ocx,
then please check out my suggestion of wrapping that datetime in a Str()
function as this problem only occurs on specific versions of the control.

Kevin Williamson - Microsoft Visual Basic Developer Support
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.

--------------------
| From: "Keith Kovala" <kov...@oz-online.net>

| References: <#tJEVs3dBHA.1456@tkmsftngp04>
<K7A7mNE...@cppssbbsa01.microsoft.com>

| Subject: Re: MSCAL (Calendar Control) causing a run-time error

| Date: Thu, 29 Nov 2001 01:05:48 -0600
| Lines: 157
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
| Message-ID: <OQ7agSKeBHA.2340@tkmsftngp05>

| Newsgroups: microsoft.public.vb.controls
| NNTP-Posting-Host: wks-65-27-97-119.kscable.com 65.27.97.119

| Path: cppssbbsa01.microsoft.com!tkmsftngp01!tkmsftngp05
| Xref: cppssbbsa01.microsoft.com microsoft.public.vb.controls:121531
| X-Tomcat-NG: microsoft.public.vb.controls

[Keith Kovala]

I will keep the str() in mind, but all systems are working now with the
unregistering of the mscal.ocx first and then installing. It just seems odd
that while the mscal I had included was newer, and yes PDW should have
installed it, and the file was physically present in the system drive, it
wasn't until I unregistered it and then placed the file in the system dir
again either manually and then registering or via an install would the
application using the control then works.

Thanks again for everything.

"Kevin Williamson" <kwill...@microsoft.com> wrote in message

news:YrlfNxS...@cppssbbsa01.microsoft.com...

[Kevin Williamson]

Keith,

You may want to take a look at the following KB article for why the mscal
control did not get registered by the PDW:
Q208699 - PRB: Error "$(DllSelfRegisterEx) Could Not Be Registered"

To find a KB article you can type "MSKB articlenum" into Internet
Explorer's Address Bar (without the quotes) or you can go to
http://support.microsoft.com.

Kevin Williamson - Microsoft Visual Basic Developer Support
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.

--------------------
| From: "Keith Kovala" <kov...@oz-online.net>

| References: <OQ7agSKeBHA.2340@tkmsftngp05>
<YrlfNxS...@cppssbbsa01.microsoft.com>

| Subject: Re: MSCAL (Calendar Control) causing a run-time error

| Date: Thu, 29 Nov 2001 21:18:29 -0600
| Lines: 237

| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

| Message-ID: <uZRfJ4UeBHA.1544@tkmsftngp03>

| Newsgroups: microsoft.public.vb.controls
| NNTP-Posting-Host: wks-65-27-97-119.kscable.com 65.27.97.119

| Path: cppssbbsa01.microsoft.com!tkmsftngp01!tkmsftngp03
| Xref: cppssbbsa01.microsoft.com microsoft.public.vb.controls:121600
| X-Tomcat-NG: microsoft.public.vb.controls

[Keith Kovala]

Kevin, I know your email address below just bounces, so I thought I'd share
this email with you that I received this morning:

-----Original Message-----
From: Mat Hepton [mailto:mhe...@divestco.com]
Sent: Wednesday, December 19, 2001 9:34
To: kov...@oz-online.net; kwill...@microsoft.com
Subject: MSCal Automation Error.

Just wanted to thank you two guys for your recent (and well

presented) UseNet thread regarding problems with MSCal

registration and the errors that go along with that.

I haven't had a chance to implement your solutions yet but I

appreciate the guidance. This one could have been a very

frustrating issue to kill. Thanks for sharing.

-mat hepton

@divestco.com

"Kevin Williamson" <kwill...@microsoft.com> wrote in message

news:71wEjDc...@cppssbbsa01.microsoft.com...

[Kevin Williamson]

Very cool :). Thanks Keith. It is always nice to know that the efforts we
put in here really do help a large group of people.

The kwill...@microsoft.com bounces because it is not a real email
address specifically to keep spam and junk from coming to us. If you need
to get in touch with me you can use kevinwi...@hotmail.com. You may
also want to pass that on to Mat Hepton if he has any more problems.

Kevin Williamson - Microsoft Visual Basic Developer Support
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.

--------------------
| From: "Keith Kovala" <kov...@oz-online.net>

| References: <uZRfJ4UeBHA.1544@tkmsftngp03>
<71wEjDc...@cppssbbsa01.microsoft.com>

| Subject: Re: MSCAL (Calendar Control) causing a run-time error

| Date: Wed, 19 Dec 2001 09:45:19 -0600
| Lines: 358

| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

| Message-ID: <uOv0ASKiBHA.2200@tkmsftngp05>

| Newsgroups: microsoft.public.vb.controls
| NNTP-Posting-Host: wks-65-27-97-119.kscable.com 65.27.97.119

| Path: cpmsftngxa07!tkmsftngp01!tkmsftngp05
| Xref: cpmsftngxa07 microsoft.public.vb.controls:121920
| X-Tomcat-NG: microsoft.public.vb.controls