ACC1x: Error When Using OpenQueryDef Method on Parameter Query

 Last reviewed: June 6, 1997
Article ID: Q100147
The information in this article applies to:
  • Microsoft Access versions 1.0, 1.1

SYMPTOMS

When you are using the OpenQueryDef method on a parameter query, the error message "Couldn't Find Object" appears when you re-create the sample code on page 137 of the Microsoft Access "Introduction to Programming" manual.

CAUSE

There are three likely causes for this error message:

  • The name of the query you are trying to open is misspelled
  • The parameter is misspelled
  • The parameter is not explicitly defined

In the sample code on page 137, both the query name and the parameter are misspelled.

RESOLUTION

The following sample function is a correction to the errors in the sample on page 137 of the Microsoft Access "Introduction to Programming" manual: 

   '*****************************************************************
   ' Declarations section of the module
   '*****************************************************************
   Option Explicit

   Function TestQP ()
      Dim db As Database, Q As QueryDef, DataRecs As Dynaset
      Set db = CurrentDB()
      Set Q = db.OpenQueryDef("Products by Category (Parameter)")
      Q![Enter a category id:] = "COND"    'This is an explicit parameter

      Set DataRecs = Q.CreateDynaset()
      DataRecs.Close
      Q.Close
   End Function

Keywords : DcmMnl kberrmsg kbprg PgmOthr
Version : 1.0 1.1
Platform : WINDOWS
Hardware : X86
Issue type : kbdocerr

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: June 6, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.