ACC: OLE Objects Seem to Be Acceptable Filter Criteria

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

SYMPTOMS

Advanced: Requires expert coding, interoperability, and multiuser skills.

Microsoft Access erroneously allows you to use OLE objects as filter criteria. If you attempt to do so, you may receive the following misleading error message:

   Record is too large.

CAUSE

Microsoft Access does not currently allow you to use OLE objects as filter criteria.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access versions 1.0, 1.1, and 2.0. This problem no longer occurs in Microsoft Access version 7.0; you can use Is Null or Not Null with the query by form (QBF) filter.

MORE INFORMATION

Steps to Reproduce Problem

  1. Using the sample database NWIND.MDB, create a new form called Form1 that is bound to the Employees table.

  2. Drag the Photo field to the form.

  3. From the View menu, choose Form.

  4. Leaving Form1 open, open the Employees form.

  5. From the Records menu, choose Edit Filter/Sort.

  6. Add the following line to the filter criteria:

          Photo = Forms!Form1!Photo
    

  7. From the Records menu, choose Apply Filter/Sort. Note that you receive the following error message:

          Record is too large
    


Additional query words: forms ole
Keywords : IntpOle kberrmsg
Technology : kbole
Version : 1.0 1.1 2.0
Platform : WINDOWS
Hardware : X86
Issue type : kbbug
Resolution Type : kbfix


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.