Interesting, not sure I could answer that without playing with the data.
Try this as a filter
set to true
I think the problem exists ONLY when I use TDS to get to the data.
No problem if I connect directly to MS SQL Server or use an export-to-Excel of the same data.
I am investigating more....
I don't like to say that the TDS is "corrupted" but it appears that way.
If I connect to the SQL Server and "Add to Saved Data Sources..." to create a brand new TDS and then reopen this new TDS, the problem does NOT exist.