>Thank you. The problem was that I was trying to move an employee number field (int) with a value of 18782 into a decimal(4). But the error messages would not give you the field name. is there a better way of catching this type of errors?

Not that I know of, unless you want to parse through all the field types. ADO is not nearly as friendly as VFP. I've gotten spoiled by VFP's data engine. Everything else is a PITA for me.

I did VB6 COM with ADO for 5 years...I hated the error messages. I had to have a cheat sheet... "Ok, this bizzare error message means we are missing a node in the XML"