M
Michelle Meyer
Hello:
A client recently upgraded to 2007
Her forms have several different combo boxes used to filter records. Behind
the combo boxes are macros. Each macro has two actions.
Action 1: RunCommand - The command is RemoveFilterSort
Action 2: ApplyFilter - A different filter is applied depending on the combo
box in use.
Here's the problem. These macros worked great until they upgraded to 2007.
Now, the 2007 version is not removing the filter. It appears to at first.
If the first search is for John Doe and the second search is for Jane
Johnson, Jane Johnson's search always goes back to John Doe. I actually have
to go into the form properties and delete the SQL statement in the FILTER
property of the form.
So..... I thought to myself...... I'll just do a work-around and change the
RemoveFilterSort command in the macro to a SetProperty and set the FILTER
property of the form to NULL before applying a filter. But, alas, Microsoft
saw fit to take the SetProperty action out of its Macro options. Also, I
cannot use the SetProperty action in the Visual Basic Modules either.
Has anyone else run into this? If so, how are you reworking all your
filters?
A client recently upgraded to 2007
Her forms have several different combo boxes used to filter records. Behind
the combo boxes are macros. Each macro has two actions.
Action 1: RunCommand - The command is RemoveFilterSort
Action 2: ApplyFilter - A different filter is applied depending on the combo
box in use.
Here's the problem. These macros worked great until they upgraded to 2007.
Now, the 2007 version is not removing the filter. It appears to at first.
If the first search is for John Doe and the second search is for Jane
Johnson, Jane Johnson's search always goes back to John Doe. I actually have
to go into the form properties and delete the SQL statement in the FILTER
property of the form.
So..... I thought to myself...... I'll just do a work-around and change the
RemoveFilterSort command in the macro to a SetProperty and set the FILTER
property of the form to NULL before applying a filter. But, alas, Microsoft
saw fit to take the SetProperty action out of its Macro options. Also, I
cannot use the SetProperty action in the Visual Basic Modules either.
Has anyone else run into this? If so, how are you reworking all your
filters?