PRB: Distribution of MSCAL Control in Visual Basic Application

Last reviewed: October 13, 1998
Article ID: Q178359

The information in this article applies to:

Microsoft Visual Basic Professional and Enterprise Editions for Windows, version 5.0

SYMPTOMS

When you are using the Visual Basic Setup Wizard to install an application, one of 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 does not ship with Visual Basic. The Calendar control ships as part of Microsoft Access or may be downloaded for free from the following URL:

   http://www.microsoft.com/officedev/freestuff/mscaldl.htm

RESOLUTION

In the VB5dep.ini file backwards compatibility section, add the following lines:

   [MSCAL.OCX]
   Register=$(DLLSelfRegister)
   Dest=$(WinSysPath)
   Uses1=

After the changes above have been added, use the Setup Wizard again to create the setup application.

NOTE: If a setup template is being used to recreate the setup, the template needs to be edited also. Open the projects *.SWT file in Notepad and edit the mscal.ocx line to read DLLSelfRegister instead of DLLSelfRegisterEx, and then recompile the setup.

STATUS

Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

REFERENCES

EULA (End User License Agreement) that ships with the products.

Additional query words: kbVBp500 kbWizard kbVBp kbdss kbDSupport kbAppSetup
Keywords : kbVBp500
Version : WINDOWS:5.0
Platform : WINDOWS
Issue type : kbprb

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.