PRB: MSRDO20.OCX Not Registered When Running Application Setup

 Last reviewed: November 7, 1997
Article ID: Q176428
The information in this article applies to:
  • Microsoft Visual Basic Enterprise Edition for Windows, version 5.0

SYMPTOMS

When running an application that uses Remote Data Objects (RDO) the following error is generated: 

 "MSRDO20.OCX Not registered."
No errors were encountered when installing the application.

CAUSE

In order for RDO to be properly registered, ODBC must be installed prior to installing the Visual Basic application.

RESOLUTION

Install ODBC prior to installing the Visual Basic application that uses RDO. On the Visual Basic Product CD-ROM in the \ODBC directory is an application that will install ODBC. For Visual Studio, Disk One \VB\ODBC is the location. The ODBC installation program and it components are re-distributable.

STATUS

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

MORE INFORMATION

This problem also occurs in Visual Basic 4.0 when using MSRDO32.DLL. ODBC must be installed first.

Steps to Reproduce Behavior

  1. Create an application that includes MSRDO20.

  2. Run the application Setup Wizard to produce setup images.

  3. Install the application on a machine that does not have ODBC installed.

  4. Run the application.

REFERENCES

For Visual Basic 5.0, the "Programmer's Guide", Chapter 17 "Distributing Applications" pages 799-800. 

Keywords          : vb5all kberrmsg
Technology        : kbobdc kbrdo
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.

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