Hey,
Does a RowFilter require some 'extras' to get it to work the same as a direct SQL WHERE clause.
This statement returns massively different result sets:
((ref like 'joe b%' or (due >= '01/01/0001 00:00:00' and due < '01/01/0001 00:00:00') or description like 'joe b%' or number like 'joe b%' or instructor like 'joe b%' or owner like 'joe b%' or staff like 'joe b%' or signatory like 'joe b%') and (due >= '09/08/2014 00:00:00' and due < '16/08/2014 00:00:00')) and (importance in ('Very Important', 'Critical'))RowFilter returns 144 rows
SQL WHERE clause returns 5 rows <-- expected
The .NET DataSet is based on a single table query - the same table that I'm using directly in SQL, so the source data is identical.
I think it might be:
- parentheses related in the RowFilter. If so, I can't figure it out!
- the 'invalid' date for the first due filter (01/01/0001 00:00:00) that .NET doesn't like whereas SQL might be happy with
- the due column in the table is a date only column. Maybe it works in SQL because it knows date only values, whereas .NET might not
Any suggestions?
Thanks