Robert says: "For that matter, IIRC, if you create a DDT.ADODriver object, it's a
static object, not dynamic. So, even if the data changes after the
fact, it should still contain your "original" values."
Yes I considered doing that. If I created a static ado recordset, I could do the same thing. But I was concerned about the recordset / ddt driver "should" still contain my original values. This is a high risk area of the system. I have done no third party software validation on ADO (OMG I so don't want to do that), so I decided this little extra bit is not too burdensome.
Thanks for your help!