How many people are aware that you can now filter out duplicate data?
Should not any project in any language do that. Isn't that part of the housekeeping strategy any experienced programmer would include in the project. You don't need a software tool to do that - what you need are people that develop the data sets and GUI the "duplicate" data came from to start doing their job.

Is allowing duplicate data to make it to a database an acceptable programming practice. I'd fire the guys on the other side of the data set!

Over a year ago, someone complained on this forum (I don't recall who) about the amount of code it took to filter out duplicate rows. You can now do that in ADO.NET 2.0.

How big and sluggish will future tools be if less than professional behavior (over sights - omissions - the arrogance of ignorance) is accepted because a tool vendor will add the smarts. Duplicate data is the problem - sloppy programming is the problem - the fact that a tool will display duplication errors is NOT the problem.

Here the hooK: NET ADO is good because it hides errors in the data. The fact that a journal entry will be posted twice because of the duplication is second on to the concerns one may have about seeing duplicate data.

Don't thinks have to be perfect. Can we trust tool set gimicks? That WMF backdoor story is still ringing in my noodle. Are we supposed to use our judgement and take control to assure our users don't see duplicate data, not because we can filter it out with this or that - but because there is no duplicate data in their database. Should we 86 our professional standerds and ethics because our boo-boos will be hidden by a feature?