I failed a DB checkpoint intentionally just to see how the results look.
I got the below:
[ QUOTE ]
Standard Checkpoint "DbTable": Failed
Date and Time: 1/4/2008 - 17:09:31
Verification type: String Content. Settings: Exact match - ON; Ignore space - ON; Match case - OFF. Results: Checked 15 cells; Succeeded: 14; Failed: 1
[/ QUOTE ]
Honestly this is useless, because it's not showing the unmatched values (actual vs. expected) it doesn't even mention the values row, colomn?
So it's telling you that it failed but donít tell why it's failing?!
nevertheless it's not showing the DB name and/or the table name
any way to enhance the DB checkpoint ?
"I realize it's an error, but no one is going to try to do that!"
From "Top 10 Stupid Comments from Developers".
In these cases, you're probably best off creating your own db checkpoint. You can open an ADO connection and recordset yourself, and then do whatever validation you want. Admittedly, it's a bit more work, but gives tons more flexibility.