Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Problem with MS Calendar Control in VB6

782 views
Skip to first unread message

Dave

unread,
Apr 1, 2005, 11:43:06 AM4/1/05
to
I'm trying to use the MS Calendar Control in a VB6 app, and it works fine on
my development PC.

But when I deploy it on my user's PC, the dates in the grid portion of the
calendar show up as 1 dot in the top left corner of each cell, rather than a
readable number. The same thing happens to the month and year in the top left
corner of the calendar.

I've tried adjusting colours, fonts, font size, depth (ie, sunken, raised or
flat), but nothing fixes the problem. Has anyone else encountered this
"feature" and know how to fix it?

Thanks
Dave

Jim Carlock

unread,
Apr 4, 2005, 8:35:43 AM4/4/05
to
The mscal.ocx control is a Microsoft Office control. It's not a
redistributable as well. If you feel you need another control there
is also a MonthView control found here:

Components:
Microsoft Windows Common Controls-2 (mscomct2.ocx).

Could you provide us with the operating systems of both systems?
And the version of the control on each system?

Hope that helps somewhat.

--
Jim Carlock
Please post replies to newsgroup.

Mona

unread,
Apr 4, 2005, 8:36:05 AM4/4/05
to

Hello Dave,

Please note that we do not have any such reported issues with the MSCalander control and as you
said that it is working fine on your development machine, it seems to be an issue with the packaging
of your application. Whenever you package an application, it carries all the information about references
being set to your control in your application to the client machine. I would suggest you to package your
application by using the standard packaging wizard like the "Package and Deployment Wizard" or the "Install Shield".

Please make sure that you include all the dependency files (You can do so with the help of the dependency walker).

http://www.dependencywalker.com

I hope this helps

Mona[Grapecity]

 

dejal

unread,
Apr 6, 2005, 9:27:21 AM4/6/05
to


For what it's worth, I've got the same problem on 1 machine. Works
fine on 4 others. Bad machine is XP, the good machines are 3 XP and 1
Windows 2000.
I've got about 10 other pcs that I don't know the answer to yet.

The program has 2 calendar controls in it, the 1st has good date #s but
tiny date and year, the 2nd calendar control has tiny everything.

I have another program that has 2 calendars on it and the same machine
shows both
calendars in that program just fine. I haven't figured out what the
diffs between the to programs are yet.

Sergito

unread,
Apr 14, 2005, 8:58:10 PM4/14/05
to

I have the exact same problem on two machines that are running wi ndows
2000 SP4. The version of MSCAL.OCX is 10.0.0.4024. I have 3 machines
that are running XP and they don't have that same problem with the
application. Any info will be helpful.

Thanks,

Sergio

--
Sergito
------------------------------------------------------------------------
Posted via http://www.codecomments.com
------------------------------------------------------------------------

Jim Carlock

unread,
Apr 14, 2005, 8:44:45 PM4/14/05
to
It looks like your MSCAL.OCX is from Office SP2. There's an Office
SP3 available as well.

http://support.microsoft.com/kb/832671

Hope this helps.

--
Jim Carlock
Please post replies to newsgroup.

"Sergito" <Sergito...@mail.codecomments.com> wrote:

I have the exact same problem on two machines that are running Windows

Pamela Fuller

unread,
Nov 9, 2006, 9:01:14 AM11/9/06
to

I had a similar problem and found that an Office Update on my
development machine used a newer version of MSCAL.OCX (found in my
“C:\Program Files\Microsoft Office\OFFICE11” directory). Once I
unregistered it (using regsvr /u) and reregistered the previous version
(found in my “C:\WINNT\system32” directory) the problem went away.

Might try checking the version of the MSCAL.OCX on both the development
machines and the machines the application is deployed on to be sure they
have the same versions registered.


Jim Carlock wrote:
> *It looks like your MSCAL.OCX is from Office SP2. There's an Office
> SP3 available as well.
>
> [url]http://support.microsoft.com/kb/832671[/url]


>
> Hope this helps.
>
> --
> Jim Carlock
> Please post replies to newsgroup.
>
> "Sergito" <Sergito...@mail.codecomments.com> wrote:
>
> I have the exact same problem on two machines that are running
> Windows
> 2000 SP4. The version of MSCAL.OCX is 10.0.0.4024. I have 3
> machines
> that are running XP and they don't have that same problem with the
> application. Any info will be helpful.
>
> Thanks,
>
> Sergio
>
>
>
> --
> Sergito
> ------------------------------------------------------------------------

> Posted via [url]http://www.codecomments.com[/url]
> ------------------------------------------------------------------------
> *

--
Pamela Fuller

zaism...@gmail.com

unread,
Mar 13, 2014, 1:36:32 AM3/13/14
to
I'm sure these above problem has been solved along time ago, but today I also found the same problem and it took a few days to solve. I share, hopefully usefull for others. What I did:

1. Download mscal.ocx from: http://www.dll-download-system.com/docman/ocx-files/2.html?limit=5&limitstart=25&dir=DESC&order=name

2. Extract mscal.zip and copy to c:\windows\systems32\

3. Run "REGSVR32 mscal.ocx" on Administrator command prompt window only, if you run "REGSVR32 mscal.ocx" on normal command prompt window, it appears ".... was loaded but the call to DllRegisterServer failed with error code 0x80004005", by: Go to Start --> All Programs --> Accessories, right-click Command Prompt, and then click Run as Administrator

4. In the black command line window, move to path c:\windows\systems32, use the command "REGSVR32 mscal.ocx" to register the file.

6. Try to run the application again.

by: zulkhairi ali ismai, aceh, indonesia, zaism...@gmail.com

ykuma...@gmail.com

unread,
Oct 22, 2016, 11:34:57 AM10/22/16
to
anyone provide me GUI of ATM in vb6.
thamx
0 new messages