ACC1x: "#Error" Message with Second Instance of Microsoft Access

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

SYMPTOMS

In Microsoft Access, you can create and run a query with an expression. However, if that expression uses an Access Basic function, a second instance of Microsoft Access will cause a "#Error" or "#Name" error message to appear in the expression field in any query, form, or report that references that field.

RESOLUTION

Close the query, form, or report and then reopen it to refresh the value. Pressing F9 will not refresh the value.

STATUS

This problem no longer occurs in Microsoft Access version 2.0.

MORE INFORMATION

Steps to Reproduce Problem

  1. Open the sample database NWIND.MDB and then open the Category List query in Design view.

  2. Add the following field to the query:

          Field: Expr1: Len([Category Name])
    

  3. Run the query.

  4. Minimize Microsoft Access.

  5. Open a second instance of Microsoft Access.

  6. Close the second instance of Microsoft Access.

  7. Restore the first instance of Microsoft Access. Note that the "#Error" message now appears in the Expr1 field.

REFERENCES

For more information about the "#Error" and "#Name" error messages, search for "error values" then "Error Values" using the Microsoft Access Help menu.


Additional query words: pounderror poundname
Keywords : kbusage QryTotal
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.