ACC: Installing Access 95 or 97 Breaks 2.0 Calendar ControlLast reviewed: June 4, 1997Article ID: Q161865 |
The information in this article applies to:
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, you should first make a backup copy of the registry files (System.dat and User.dat). Both are hidden files in the Windows folder.
SYMPTOMSAdvanced: Requires expert coding, interoperability, and multiuser skills. If you install Microsoft Access 7.0 or 97 on a computer that contains Microsoft Access 2.0 and Microsoft Access Developer's Toolkit version 2.0, you may receive the following error message when you try to add a Calendar Control object to a form or report:
There is a problem with the registration database. CAUSEWhen you install Microsoft Access 7.0 or 97, the Setup program creates the following key under HKEY_CLASSES_ROOT in your Windows Registry:
CLSID\{399A11C0-CFAC-101A-B8A0-00608CB87234}\AutoConvertTo
The key contains the CLSID for the 32-bit Calendar control included with
Microsoft Access 7.0 and 97. It tells Microsoft Access to convert calls to
the 16-bit Calendar control automatically to the 32-bit Calendar control so
your Microsoft Access 2.0 database will convert to a newer version more
easily. However, when you try to insert the Calendar control in version
2.0, Microsoft Access tries instead to insert the 32-bit equivalent, which
is incompatible with 16-bit Microsoft Access 2.0.
RESOLUTIONIf you want to continue to use the Calendar control in version 2.0, you can edit the Windows Registry and rename the AutoConvertTo key. The following steps show you how. WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Microsoft Windows 95 or Microsoft Windows NT. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the Changing Keys And Values online Help topic in Registry Editor (Regedit.exe). Note that you should make a backup copy of the registry files (System.dat and User.dat) before you edit the registry.
MORE INFORMATIONThis problem only occurs when you have Microsoft Access 2.0 and Microsoft Access Developer's Toolkit version 2.0 on your computer, and then you set up Microsoft Access 7.0 or 97 in a separate folder on the same computer. If you follow the steps in the "Resolution" section to change the Windows Registry key, you will encounter error messages if you try to convert a version 2.0 database with a Calendar control in Microsoft Access 7.0 or 97. You can follow the steps again to rename the AutoConvertToX Registry key back to AutoConvertTo before you convert your database. If the Registry key is missing when you convert your version 2.0 database, you may receive the following error messages.
Using Microsoft Access 7.0
The following warning occurs during conversion of your Microsoft Access
2.0 database:
One or more functions or reports contains a 16-bit OLE custom control
with no 32-bit equivalent. These controls will not function properly
under Microsoft Windows 95 or Microsoft Windows NT.
After the database is converted, you receive the following error when
you open an object that contains the Calendar control:
The object application isn't registered.
Using Microsoft Access 97
The Microsoft Access 2.0 database converts without any warnings, but
you receive the following error message when you open an object that
contains the Calendar control:
There is no object in this control.
Steps to Reproduce Behavior
REFERENCESFor more information about using the Calendar control in Microsoft Access 2.0, search the OLE Calendar Control Help file, Msacal20.hlp.
|
Additional query words: MSACAL70.OCX MSCAL.OCX MSACAL20.OCX setup setup.exe
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |