ACC: Error Using More Than 2000 Characters in WhereCondition of OpenReport

Article translations Article translations
Article ID: 184948 - View products that this article applies to.
This article was previously published under Q184948
This article has been archived. It is offered "as is" and will no longer be updated.
Moderate: Requires basic macro, coding, and interoperability skills.

Expand all | Collapse all

On This Page

Symptoms

When you run a procedure that contains the OpenReport method of the DoCmd object, and you use the WhereCondition argument to pass a string that contains more than 2000 characters, the report may not open. You may also receive one of the following error messages:
- Run-time error '2465':

Microsoft Access can't find the field <field name> referred to in your expression.

You may have misspelled the field name, or the field may have been renamed or deleted.

- Run-time error '3464':

Data type mismatch in criteria expression.

- No current record.

- Out of memory.

Note that the number of characters in the WhereCondition argument that causes this behavior may vary. For example, the problem may not occur until the length of the WhereCondition argument exceeds 2048 characters.

Resolution

You can use two methods to filter a report without limitation on the size of the WHERE clause.

Method 1

Instead of using the WhereCondition argument, use the FilterName argument of the OpenReport method to pass the name of a saved query. This method allows you to filter a report without limitation on the size of the WHERE clause.

Method 2

Use the Open event to set the RecordSource property of the report to the SQL statement or to a saved query.

Note that the number of characters in a cell in the query grid is limited to 1,024. If the SQL statement of the query results in more than 1,000 characters in a cell in the query grid, and if you use the FilterName argument to pass the name of that query to the OpenReport method, you may see unexpected behavior.

Status

Microsoft has confirmed this to be a problem in Microsoft Access versions 7.0 and 97.

More information

Steps to Reproduce Problem


  1. Start Microsoft Access and open the sample database Northwind.mdb.
  2. Use the AutoReport: Columnar wizard to create a new report based on the Shippers table. Save the report as rptWhereTest.
  3. Create a new module, and type or paste the following procedure into the Module window:
          Sub ReportWhereTest()
    
             Dim strPWhr As String
    
             ' Build a Where clause that is 2046 characters long.
             strPWhr = "[Phone] in ('" & String(2031, "a") & "')"
    
             ' Show how long the WhereCondition is.
             MsgBox Len(strPWhr) & " Characters"
    
             ' Open the report with the WhereCondition.
             DoCmd.OpenReport "rptWhereTest", acViewPreview, , strPWhr
    
             ' If you are using Microsoft Access 7.0, comment out the
             ' previous line that contains the OpenReport method by typing
             ' an apostrophe at the beginning of that line. Then remove
             ' the apostrophe from the beginning of the following line:
             ' DoCmd.OpenReport "rptWhereTest", acPreview, , strPWhr
    
          End Sub
    						
  4. Compile and save the code.
  5. Run the procedure.

    Note that the code fails silently or that you receive one of the error messages described in the "Symptoms" section of this article.

References

For more information about the OpenReport method, search the Help Index for "OpenReport method," or ask the Microsoft Access 97 Office Assistant.

Properties

Article ID: 184948 - Last Review: October 26, 2013 - Revision: 4.0
Applies to
  • Microsoft Access 97 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kberrmsg kbpending KB184948

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com