Hi Simon, thanks for looking into the problem.
Simon Oliver wrote: > But "" isn't null, it's an empty string. We use undef to insert a null > value. I was assuming empty strings were converted to SQL nulls as undefs are. I don't think that assumption was correct, and I have seen empty strings treated correctly under DBD::ODBC. But the fact remains, I received the same error (the same one you posted) from DBD::ADO whether the variables were undef or empty strings. But if no one else can reproduce that behavior, I'll assume it was something I did (maybe a data type mismatch). -phil
