PRB: SET FILTER Command Behaves Differently in a Method or EventLast reviewed: November 26, 1997Article ID: Q176657 |
The information in this article applies to:
SYMPTOMSWhen you use the SET FILTER command to control data while in a form, most of the objects in the form disappear or do not display data properly after the SET FILTER command is issued. This problem occurs when you use a variable in the evaluation clause of the SET FILTER command and the command is executed in an object's method or event. Text and combo boxes may disappear while grids and list boxes do not show any records. Tabbing or clicking the location of the objects on the form restores them to their original values.
CAUSEWhen you use a variable in a method or event, the variable goes out of scope unless the variable was available before the form was run.
RESOLUTION
STATUSThis behavior is by design.
MORE INFORMATIONNormally, a query would be used to create a subset of a table based on some value. The SET FILTER command can also be used to view that subset of data. Using a variable in the SET FILTER command in one of the object's methods or events is a problem because the variable goes out of scope after returning from the method or event. Therefore, the filter is invalid and the data resets back to all the records. Trying to use a property of the form in the SET FILTER command results in this error:
Property <property name> is not found.The SET FILTER command does not recognize a property of the form; therefore, a variable must be used.
Steps to Reproduce Behavior
|
Additional query words:
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |