G
Gary Shell
I am guessing this has been covered here before, but can't seem to find a
definitive solution in my dejanews searches.
I have an Access ADP app that uses the "DoCmd Openform" construct that
passes a "where clause" to the form being opened. This gets passed, of
course, as a ServerFilter property. If then switch to design view on this
"child form" and make any adjustment, like moving a control and then save
the form, the damn ServerFilter is saved as well, and subsequent invocations
of the form ignore the ServerFilter being passed from the "parent" and
instead use the saved filter.
I have tried setting Me.ServerFilter to '' in the form close event but that
doesn't seem to help.
I have seen some replies from Microsoft that this is a feature. HORSE
HOCKEY. It's is a major pain in the ass. One that requires scanning every
form for a persisted ServerFilter before deployment. I can not think of a
single scenario where I'd want a ServerFilter saved at design time.
How are the rest of you coping with this?
Gary Shell
definitive solution in my dejanews searches.
I have an Access ADP app that uses the "DoCmd Openform" construct that
passes a "where clause" to the form being opened. This gets passed, of
course, as a ServerFilter property. If then switch to design view on this
"child form" and make any adjustment, like moving a control and then save
the form, the damn ServerFilter is saved as well, and subsequent invocations
of the form ignore the ServerFilter being passed from the "parent" and
instead use the saved filter.
I have tried setting Me.ServerFilter to '' in the form close event but that
doesn't seem to help.
I have seen some replies from Microsoft that this is a feature. HORSE
HOCKEY. It's is a major pain in the ass. One that requires scanning every
form for a persisted ServerFilter before deployment. I can not think of a
single scenario where I'd want a ServerFilter saved at design time.
How are the rest of you coping with this?
Gary Shell