I have a simple form displaying a list of records. At the top of the form is a combo box in which the user can type a search string, then click a "find" button. The find button's click event contain code that sets the form's filter property:
Me.Filter = "(myFieldName Like '*" & Me.FindTxt.Value & "*')"
Me.FilterOn = TRUE
This form works great in an Access database (MDB), but when I port it over to a project version of the same application (ADP), it filters everything out. (The only change made to the form is modifying the syntax on RecordSource to reference the table as ADP instead of ODBC.) No errors are generated, it just returns no records. I didn't want to use the ServerFilter property because that would increase network traffic (I'd have to have the server process the filter then retransmit the dataset).
Does anyone know why the regular filter property wouldn't work the same in ADP?
Me.Filter = "(myFieldName Like '*" & Me.FindTxt.Value & "*')"
Me.FilterOn = TRUE
This form works great in an Access database (MDB), but when I port it over to a project version of the same application (ADP), it filters everything out. (The only change made to the form is modifying the syntax on RecordSource to reference the table as ADP instead of ODBC.) No errors are generated, it just returns no records. I didn't want to use the ServerFilter property because that would increase network traffic (I'd have to have the server process the filter then retransmit the dataset).
Does anyone know why the regular filter property wouldn't work the same in ADP?