Hi, Rob!
Yes, the commenting-out of the "On Error" statement was intentional, as part of my testing.... It seems the "cnv.Convert()" isn't returning control at all when this error occurs. That's ok... I can deal with this in a whole different way, I think...
My take on it at this point is to remove the primary key from the table so there's no attempt to filter dups, and do that after the fact with a bit of VBA code... sound reasonable? There are 2 fields (3 if I decide not to combine the Date/Time into 1 field) that will identify a record as unique. I figure that there should be a way to select unique on those 3, and more the results into another table in which NO dups are allowed... Yes?
Thanks again for your interest in, and assistance with, this weirdness....
Joe (should this maybe get its own thread?) Parker
JP
|