FreeTDS Development Group

[Brian Bruns <camber AT ais.org>]

Not so, Microsoft broke big endian clients with respect to datetime and
money fields.  So, I'm wondering if they fixed it in a later service pack.

Brian

On Tue, 27 Mar 2001, Mark J. Lilback wrote:

> The server is on an x86 box running NT, SQL Server 7.00.623. My 
> client is big-endian, but endian-ness should only effect bytes in a 
> word, right?
> 
> 
> >Are you running on a big-endian platform?  If so, what service pack are
> >you running on the SQL Server?
> >
> >Brian
> >
> >
> >On Tue, 27 Mar 2001, Mark J. Lilback wrote:
> >
> >>  Has anyone else run into problems with using SYBDATETIME values?
> >>
> >>  I'm talking to SQL Server 7 using TDS 4.2 and everytime I use dbdata
> >>  to get a value as TDS_DATETIME, the structure seems to be reversed
> >>  (i.e. the first 32 bytes are the time and the last 32 bytes are the
> >>  days). SYBDATETIME4 works fine, but not SYBDATETIME.
> >>
> >>  I was going to add code to swap these two, but I wanted to confirm
> >>  that this is a problem and I'm just not seeing something correctly.
> 
>