[snip] > > BTW, SQLConnect (the ODBC 1.0 function DBD::ODBC can use) has > a limit on the size of the string you can pass in the first > argument (I think it is 32). DBD::ODBC used to get around > this by looking for "DSN=" at the start of the string and > using SQLDriverConnect instead. I'm not sure without > examining the source again that a connection string starting > with "DRIVER=" will go to SQLDriverConnect (which it needs to).
FYI -- DBD::ODBC checks for DSN= or a strlen(DSN) > SQL_MAX_DSN_LENGTH and thus should avoid the call to SQLConnect. And, the current version only falls back to SQLConnect if SQLDriverConnect fails. I believe this is is "safe" behavior, but any suggestions you have, Martin, are most welcome. Thanks, Jeff
