D
Don Barton
I have a mde 2003 database using the Runtime 2007. I change the
extension on my mde to accdr, and everything loads fine. When the
user logs on, I have a custom form that allows for building a query
for filtering the record set. For example, in the Last Name field, if
the user puts in "A", then all the records with a Last Name that
starts with A are shown. Using the runtime, instead of seeing all the
records with Last Name begining with A, I get a blank form. At the
bottom of the form, along with the record navigation buttons, is a
search and filter button. These are hardcoded into the Runtime. The
filter button is highlighted. If I press the filter button to turn it
off, the results of my filter, all last names with A, are shown. Why
is the runtime trying to filter my filter? Note, even if I don't put
in any filter parameter, I still get the filter button highlighted,
and a blank form. If I turn it off, I get my entire record set, which
is how it is suppose to work. Using Access 2003 I don't have this
problem.
Don
extension on my mde to accdr, and everything loads fine. When the
user logs on, I have a custom form that allows for building a query
for filtering the record set. For example, in the Last Name field, if
the user puts in "A", then all the records with a Last Name that
starts with A are shown. Using the runtime, instead of seeing all the
records with Last Name begining with A, I get a blank form. At the
bottom of the form, along with the record navigation buttons, is a
search and filter button. These are hardcoded into the Runtime. The
filter button is highlighted. If I press the filter button to turn it
off, the results of my filter, all last names with A, are shown. Why
is the runtime trying to filter my filter? Note, even if I don't put
in any filter parameter, I still get the filter button highlighted,
and a blank form. If I turn it off, I get my entire record set, which
is how it is suppose to work. Using Access 2003 I don't have this
problem.
Don