ACC1x: Error Using SQL in Report RecordSource Property

 Last reviewed: May 14, 1997
Article ID: Q93293
The information in this article applies to:
  • Microsoft Access versions 1.0, 1.1

SYMPTOMS

You receive the following error message when you try to use a valid SQL statement as the RecordSource in a report: 

   This report is bound to a table or query that doesn't exist:
   '<SQL statement>'.

RESOLUTION

Create a query using the SQL statement, and then base your report on that query.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access versions 1.0 and 1.1. This problem no longer occurs in Microsoft Access version 2.0.

MORE INFORMATION

Steps to Reproduce Problem

  1. Open the sample database NWIND.MDB.

  2. Open the Category List query in Design view.

  3. From the View menu, choose SQL.

  4. Select the contents of the SQL window. Then, choose Copy from the Edit menu.

  5. Choose Cancel to close the SQL dialog box. Then close the Category List query.

  6. Open a new unbound form, and paste the SQL statement into the form's RecordSource property by choosing Paste from the Edit menu.

  7. View the form in Form view.

  8. Open a new unbound report, and paste the SQL statement into the report's RecordSource property by choose Paste from the Edit menu.

  9. Preview the report.

Note that you do not receive an error message in step 7, but you do in step 9. You can use a valid SQL statement as the RecordSource in a form, but not in a report.

Keywords : kberrmsg kbusage RptProp
Version : 1.0 1.1
Platform : WINDOWS
Hardware : X86
Issue type : kbbug
Resolution Type : kbworkaround

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