FreeTDS Development Group

["Michael Horowitz" <michael.horowitz AT storagenetworks.com>]

>From a big endian machine, I have to use "emulate-little-endian" to
connect to SQL Server 7 and above with either TDS 4.2 or 7.0, or datetime
fields are wrong because the bytes are backwards.  I thought that the
whole point of "emulate-little-endian" was because SQL Server didn't
properly swap bytes for big endian machines.  I tried using "swap broken
dates", but that didn't do anything.

I thought that without "emulate-little-endian" a properly working SQL
Server is supposed to do the swapping of the bytes?  Is that only for
datetime and other data fields, and not for the message number?  If that
is the case, then I guess you should only swap those bytes if
"emulate-little-endian" is off.

--Mike

> >Hey Mark,
> >
> >I was wondering if you looked into any of this stuff in my last email?
> 
> I haven't looked at it yet, but in the configuration I'm using (TDS 
> 4.2, no emulate-little-endian, SQL Server 7), error codes needed to 
> be swapped or error messages never get reported.
> 
> I'm planning on taking a look this weekend... just got hung up with 
> some other things at work.
> 
> -- 
> __________________________________________________________________________
>                                    "They that can give up essential liberty
> Mark J. Lilback                    to obtain a little temporary safety
> <mark AT lilback.com>                 deserve neither liberty or safety."
> http://www.lilback.com/                               -- Benjamin Franklin