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

'MSCAL. OCX. not correctly registered file is missing or invalid.'

543 views
Skip to first unread message

Perry J Hemmings

unread,
Oct 1, 1998, 3:00:00 AM10/1/98
to
Can anyone help with this problem please, I have a small
application that I use a MSCalendar.OCX which when I
developed worked perfectly on my PC, but when I put it
on my Clients PC I got a message:

'Component MSCAL. OCX. not correctly registered file is missing or
invalid.'

Any ideas?

Perry


herr...@my-dejanews.com

unread,
Oct 1, 1998, 3:00:00 AM10/1/98
to
You should copy mscal.ocx to the client's \windows\system32 directory. Then
from a DOS COMMAND session, change to the system32 directory and type
"REGSVR32.EXE MSCAL.OCX". If all goes well, you then receive a message box
noting that the registration was successful…

Good Luck,
Raul Herrero


In article <6uv6o3$g9s$1...@mendelevium.btinternet.com>,


-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum

Johan van Niekerk

unread,
Oct 2, 1998, 3:00:00 AM10/2/98
to
Hiya

I had a similar problem and got the following fix.
Hope this helps :)

Johan

Microsoft Visual Basic Professional and Enterprise Editions for
Windows, version 5.0
---------------------------------------------------------------------
SYMPTOMS
========
When using the Visual Basic Setup Wizard to install an application, the
following errors may occur:
"c:\windows\system\$(dllselfregisterex) could not be registered
because
it could not be found."
-or-
"The dependency file for MSCAL.OCX is out of date."
CAUSE
=====
The Calendar control is part of the Office Developers Edition, not part
of
Visual Basic. In order to be in compliance with the licensing agreement,
you must have a license for Office Developers Edition.
RESOLUTION
==========
In the VB5dep.ini file backwards compatibility section, add the
following
lines:
[MSCAL.OCX]
Register=$(DLLSelfRegister)
Dest=$(WinSysPath)
Uses=1
After the changes above have been added, use the Setup Wizard again to
create the setup application.

Perry J Hemmings wrote in message
<6uv6o3$g9s$1...@mendelevium.btinternet.com>...

0 new messages