This is a hopeless question, but I figured I'd see whether or not anybody has some insight.

I have a DGV that uses the DefaultView of a datatable as it's source. The datatable is filled on program startup, and it is a simple query of a couple fields from one table with an unimpressive WHERE clause that just gets the most recent years. No joins, just a couple columns from one table. The data is also ordered on two columns.

The program runs on three computers. On two of them, it works as expected. On the third, most every name (the display value from the datatable) shows up multiple times. They are ordered properly, they just appear up to three times.

Note that on the three computers (one dev system and two deployments), the query is exactly the same.

I'm at a loss as to how one of the three can show different results, also, how that one can have duplicates when the other two do not. There are no such duplicates in the underlying data.

As I wrote this, I realized that there is one way that it might be possible, if Date.Now on the target system was wildly wrong. That's all that the WHERE clause holds, as it only takes records where the date is greater than Date.Now for reasons I won't get into. The system date on the problem system would have to be off by several days, though. That seems improbable, but it's something worth looking at.

Are there any other ways that a query can return duplicates, or that the DefaultView of a datatable can return duplicates? It would have to be something that could behave differently from one system to the next, as duplicates do not actually exist in the underlying data.