P
Paul M
A source of constant irritation with Microsoft Access is the behavior of
forms in an ADP project saving the ServerFilter property when it is set
through code in run mode. If you open a form using a WhereCondition, the
ServerFilter is set to the WhereCondition. If you subsequently flip the form
into Design Mode, make changes and then save the form, the ServerFilter
property is saved with the form and any subsequent attempt to open the form,
even if a WhereCondition is passed using the OpenForm command, results in the
saved ServerFilter being applied and any other WhereClause is ignored.
The better behavior would be for the ServerFilter property to only be saved
with the form if it was explicitly set in Design Mode or, if alike the normal
Filter property, there was a matching "ServerFilterOn" property that was set
to "off" by default to prevent the ServerFilter from being applied
universally.
forms in an ADP project saving the ServerFilter property when it is set
through code in run mode. If you open a form using a WhereCondition, the
ServerFilter is set to the WhereCondition. If you subsequently flip the form
into Design Mode, make changes and then save the form, the ServerFilter
property is saved with the form and any subsequent attempt to open the form,
even if a WhereCondition is passed using the OpenForm command, results in the
saved ServerFilter being applied and any other WhereClause is ignored.
The better behavior would be for the ServerFilter property to only be saved
with the form if it was explicitly set in Design Mode or, if alike the normal
Filter property, there was a matching "ServerFilterOn" property that was set
to "off" by default to prevent the ServerFilter from being applied
universally.