> > Thank you everyone who responded and to Tim and Jeff: > > The reason the server generates an error is because there are > 2 flags which can be set when you create the DSN: > > Use ANSI quoted identifiers > Use ANSI null, padding and warning > > And they were both selected. > > De-selecting "Use ANSI null, padding and warning" fixed the issue. > > This may only be an issue on Win32. > > Does anyone know how to check/set this attribute using DBI so > I don't have to instruct a user on changing his DSN? ( I > don't see this option mentioned in DBD::ODBC )
Sorry, there isn't a way to do this via DBD::ODBC. What you might want to do, if your scripts require a specific setting, is to generate a query (or set of queries) after the connect to validate that the settings you need are set, if not, die with an error message indicating what needs to be done. That way, you won't be half-way through a transaction and have a query fail. Regards, Jeff
