> > I was assuming empty strings were converted to SQL nulls as undefs are. > Not by DBI but maybe by your underlying DBMS?
Access 97. I believe it makes the distinction. > > But if no one else can reproduce that behavior, I'll > > assume it was something I did (maybe a data type mismatch). > No - IMHO there is something wrong with DBD::ADO when undef is passed! Absolutely. What confuses me, though, is that I set all my undef'ed vars to empty strings and still got the error. But I suspect that time was my fault, since one of those was a date.
