Ah, I looked into the odbc configuration and found "Use ANSI nulls, paddings and warnings" checked. I unchecked it, logged in, and sure enough...the trailing spaces weren't there. Thanks for the tip.
What do you use instead of ODBC? Chris -----Original Message----- From: Eric Dobbs [mailto:[EMAIL PROTECTED]] Sent: Sunday, April 28, 2002 9:49 AM To: Turbine Users List Subject: Re: Trailing Spaces in SQL Server Fields On Friday, April 26, 2002, at 03:21 PM, Chris Chew wrote: > The schema is already set as VARCHAR(32). I modified > the mysql schema that comes with the tdk to work with > MSSQL, which basically meant changing TIMESTAMP's to > DATETIMES and using a more complex "IF EXISTS" > statement. > > Any other ideas? We saw something like this with ODBC settings, but I can't remember exactly what they were (we quit using ODBC a long time ago). But I seem to remember a configuration in the ODBC control panel that padded entries with white space. Sorry I can't be more specific. -Eric -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
