>Thanks for the info, guys. I never did figure out how to get the error handler to tell me which column had the bogus data, I had to find it on my own. In case you're curious, the problem was with a date column (dLastUpdt), but not because it was empty. Apparently, our monks last worked on those proposals in the 11th century. Hmph, legacy data!


So, SQL server 7 is not Y1K compliant? :)