PRB: DAO References Not Enabled When Porting an Older VB App

 Last reviewed: October 27, 1995
Article ID: Q130646
The information in this article applies to:
  • Standard, Professional, and Enterprise Editions of Microsoft Visual Basic, 16-bit and 32-bit, for Windows, version 4.0

SYMPTOMS

A reference to any database object or method in a Visual Basic program generates the error: 

   User-defined type not defined
This error often occurs when loading your first Visual Basic version 3.0 program into Visual Basic version 4.0.

CAUSE

When you load your first Visual Basic version 3.0 project, a dialog box asks you: 

   Would you like Visual Basic to add this library reference now?
If you selected the "No for All Older Projects" button, an entry was made in your VB.INI file that says AutoReferenceDAO=1. If you remove this line, you will see the dialog box again and be able to add needed Visual Basic 3.0 project references automatically.

RESOLUTION

For the current project, choose References from the Tools menu, and select the Microsoft DAO 2.5/3.0 Compatiblity Library check box. This enables compatibility with the older syntax found in Visual Basic version 3.0 programs. Microsoft reccommends that you upgrade the syntax in your programs to the new DAO 3.0 syntax used in Visual Basic version 4.0, replacing the DAO 2.5/3.0 with the DAO 3.0.

STATUS

This behavior is by design.

Additional reference words: 4.00 2.50 3.00 vb4win vb4all
KBCategory: kbui kbprg kbprb
KBSubcategory: EnvtDes APrgDataOther

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: October 27, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.