Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

datetime problems with Jag

2 posts in General Discussion (old) Last posting was on 2000-03-15 15:47:58.0Z
Eric Pearson Posted on 2000-03-15 02:43:23.0Z
Newsgroups: sybase.public.easerver
From: "Eric Pearson" <epearson@jps.net>
Subject: datetime problems with Jag
Date: Tue, 14 Mar 2000 18:43:23 -0800
Lines: 23
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
NNTP-Posting-Host: 64.14.6.154
Message-ID: <347_Hr#txjij$GA.201@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26399
Article PK: 157068

I am having a problem with datetime fields getting changed by Jaguar when I
retrieve. This only occurs when I run against a server though (if I run
localhost it works fine). It sometimes adds a year to the date and
sometimes it adds a year and subtracts a day. (02/03/00 goes to 02/02/01).
The date is correct on the database which is MS SQL Server and we are using
odbc (since there is no native for this). We are in the process of
upgrading everything to 3.5. I ran my client against a machine with 3.5
JAGUAR though my client is running PB 7.0.1 and I saw the same results. Is
this a known bug? Is it fixed somewhere? We have the EBF's installed on
our server which is running 3.5. I tried to install the PB client 7.0.2 and
it told me that I do not have the EA STUDIO 3.0 or 3.0.1 so I could not
install this update. This message was incorrect since I have had this on my
machine for quite some time now but that is a separate issue I am trying to
resolve with SYBASE.

Any help, comments, suggestions... would be greatly appreciated as we are
going live in a few weeks and this bug is unacceptable.


Thanks
Eric


Dave Wolf [Sybase] Posted on 2000-03-15 15:47:58.0Z
Newsgroups: sybase.public.easerver
From: "Dave Wolf [Sybase]" <dwolf@sybase.com>
Subject: Re: datetime problems with Jag
Date: Wed, 15 Mar 2000 10:47:58 -0500
Lines: 39
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
NNTP-Posting-Host: dwolf-nt.sybase.com 157.133.41.72
Message-ID: <347_47#moZpj$GA.151@forums.sybase.com>
References: <347_Hr#txjij$GA.201@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26366
Article PK: 157036

Please contact support. There was a bug that would cause this and it has
been fixed. Work with support to make sure you have the right builds.

Dave Wolf
Internet Applications Division

"Eric Pearson" <epearson@jps.net> wrote in message
news:Hr#txjij$GA.201@forums.sybase.com...
> I am having a problem with datetime fields getting changed by Jaguar when
I
> retrieve. This only occurs when I run against a server though (if I run
> localhost it works fine). It sometimes adds a year to the date and
> sometimes it adds a year and subtracts a day. (02/03/00 goes to 02/02/01).
> The date is correct on the database which is MS SQL Server and we are
using
> odbc (since there is no native for this). We are in the process of
> upgrading everything to 3.5. I ran my client against a machine with 3.5
> JAGUAR though my client is running PB 7.0.1 and I saw the same results.
Is
> this a known bug? Is it fixed somewhere? We have the EBF's installed on
> our server which is running 3.5. I tried to install the PB client 7.0.2
and
> it told me that I do not have the EA STUDIO 3.0 or 3.0.1 so I could not
> install this update. This message was incorrect since I have had this on
my
> machine for quite some time now but that is a separate issue I am trying
to
> resolve with SYBASE.
>
> Any help, comments, suggestions... would be greatly appreciated as we are
> going live in a few weeks and this bug is unacceptable.
>
>
> Thanks
> Eric
>
>