ODE97: "You don't have a license" Error Using ActiveX Control

Last reviewed: November 21, 1997
Article ID: Q172859
The information in this article applies to:
  • Microsoft Office 97 Developer Edition Tools

SYMPTOMS

Moderate: Requires basic macro, coding, and interoperability skills.

When you insert an ActiveX control that shipped with the Microsoft Office 97 Developer Edition (ODE) Tools, or when you attempt to access the properties of the ActiveX control, you receive the following error message:

   You don't have the license required to use this ActiveX control.

CAUSE

Before you installed the ODE Tools, you installed an application that uses run-time versions of the ActiveX controls. If more recent versions of the files for these controls already existed on your computer when you installed the ODE Tools, the ActiveX control (.ocx) files were not updated. As a result, the corresponding dependency (.dep) files were not installed, and registry entries required to give the controls design-time functionality were not made.

RESOLUTION

You can use either of the following methods to resolve the problem, but Method 1 is the recommended resolution.

Method 1

Download the Odelic.exe file from the Microsoft Software Library.

 ~ Odelic.exe (size: 815840 bytes) 

   is a self-extracting executable file, which contains the following
   files:

   OdeOcxFx.exe    Office Developer Edition ActiveX Control Update
   Readme.txt      Readme file

Running OdeOcxFx.exe provides you with a design-time license to the ActiveX controls that ship with the ODE; it updates the registry and copies the .dep files onto your computer if they do not already exist.

For more information about downloading files from the Microsoft Software Library, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q119591
   TITLE     : How to Obtain Microsoft Support Files from Online Services

Method 2

  1. Rename Comctl32.ocx, Comdlg32.ocx, and Richtx32.ocx, which are files that are located in the Windows\System folder.

  2. Rename the Setup.stf file in the ODETools\Setup folder; the default location of this folder is C:\Program Files\Microsoft Office.

  3. Reinstall the ODE Tools.

  4. Replace Comctl32.ocx, Comdlg32.ocx, and Richtx32.ocx with the original files that you renamed in Step 1.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Office 97 Developer Edition Tools. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Scenarios in which this problem can occur include, but are not limited to:

  1. Installation of the ODE Tools after you have installed the Exchange/Outlook Wizard, which uses Comctl32.ocx.

  2. Installation of the ODE Tools after you have installed a custom application that uses a run-time version of one of the ActiveX controls. The custom application was developed in Microsoft Visual Basic version 5.0, Microsoft Visual C++ version 4.0, or Microsoft Visual FoxPro version 5.0.

  3. Installation of the ODE Tools after you have installed a custom application that uses a run-time version of one of the ActiveX controls. Microsoft Visual Basic version 5.0, Microsoft Visual C++ version 4.0, or Microsoft Visual FoxPro version 5.0 is installed on the development computer, and the Setup Wizard included with the ODE Tools was used to package the custom application.


Additional query words: soft lib
Keywords : OdeStf
Version : WINDOWS:97
Platform : WINDOWS
Issue type : kbbug
Solution Type : kbfix


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.

Last reviewed: November 21, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.