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.

Truncated zeros

3 posts in Internet Last posting was on 2001-01-17 19:22:02.0Z
jtreat Posted on 2000-11-21 20:35:46.0Z
From: jtreat@qwest.net
Date: Tue, 21 Nov 2000 15:35:46 -0500
Newsgroups: sybase.public.sqlserver.internet
Subject: Truncated zeros
Message-ID: <24F0144915050C47007123688525699E.007123788525699E@webforums>
Lines: 16
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com!webforums.sybase.com!news
Xref: forums-1-dub sybase.public.sqlserver.internet:278
Article PK: 1067336

I am using an active server page to create an ADO record set to be used to
populate a Crystal Report or a delimited text file. The record set is
generated by a stored procedure. The issue is that trailing zeros in
numeric fields are being truncated. So 1000000.000 becomes 1 and 9500.000
becomes 95. This issue does not affect string or integer data. As a
workaround I can convert the data to a string data type in the stored
procedure and it will be correct. The problem is that this could require
modifying over a hundred stored procedures. I?d much rather resolve the
issue. Because the data is correct when the stored procedure is run I
thought it would be in the ODBC drives but updating to the latest drivers
available from Sybase did not resolve the issue.

Any ideas would be appreciated.

--jet


David Berry Posted on 2001-01-17 19:22:02.0Z
From: "David Berry" <dberry@mvps.org>
References: <24F0144915050C47007123688525699E.007123788525699E@webforums>
Subject: Re: Truncated zeros
Date: Wed, 17 Jan 2001 14:22:02 -0500
Lines: 44
X-Newsreader: Microsoft Outlook Express 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Message-ID: <9Kp2P0LgAHA.300@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.internet
NNTP-Posting-Host: m1.aetna.com 206.213.251.21
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.internet:263
Article PK: 1067319

We recently had the same problem. Here's what we did and it fixed it:

The our application encountered a problem with the truncation of money
columns being displayed from active server pages (ASP) with an ODBC
connection to a Sybase database. For example, the value of 1000000.0000 was
being displayed as 1. Database inserts and updates were correctly handled.

Initially, MDAC 2.5 with SP2 was applied to the server. Unfortunately, this
did not solve the problem.

Further research revealed the above is a known problem with Sybase ODBC
11.1.1 and was corrected with EBF8252 (for NT) and EBF8253 (for Win95) and
subsequent EBFs.

After ODBC 11.1.1 EBF8513 (Sybase recommend) was applied to the server it
worked fine.

Installation of EBF8513 consisted of replacing the following three (3) dlls:
sybasnt.dll
sysybnt.dll
syutlnt.dll

jtreat@qwest.net wrote in message
<24F0144915050C47007123688525699E.007123788525699E@webforums>...
>I am using an active server page to create an ADO record set to be used to
>populate a Crystal Report or a delimited text file. The record set is
>generated by a stored procedure. The issue is that trailing zeros in
>numeric fields are being truncated. So 1000000.000 becomes 1 and 9500.000
>becomes 95. This issue does not affect string or integer data. As a
>workaround I can convert the data to a string data type in the stored
>procedure and it will be correct. The problem is that this could require
>modifying over a hundred stored procedures. I?d much rather resolve the
>issue. Because the data is correct when the stored procedure is run I
>thought it would be in the ODBC drives but updating to the latest drivers
>available from Sybase did not resolve the issue.
>
>Any ideas would be appreciated.
>
>--jet
>
>


George Saylor Posted on 2000-11-21 22:52:31.0Z
From: "George Saylor" <GMSAYLORIII@email.msn.com>
References: <24F0144915050C47007123688525699E.007123788525699E@webforums>
Subject: Re: Truncated zeros
Date: Tue, 21 Nov 2000 17:52:31 -0500
Lines: 29
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
Message-ID: <ebcnW$AVAHA.162@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.internet
NNTP-Posting-Host: 1Cust202.tnt4.baltimore.md.da.uu.net 63.16.13.202
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.internet:277
Article PK: 1067335

try setting in the advanced tab of DSN

SET ANSINULL OFF

This worked for us in a similar issue ( Crystal and truncated zeroes on
numeric fields ), solution was courtesy of Sybase tech support ( and we
can't thank them enough )

<jtreat@qwest.net> wrote in message
news:24F0144915050C47007123688525699E.007123788525699E@webforums...
> I am using an active server page to create an ADO record set to be used to
> populate a Crystal Report or a delimited text file. The record set is
> generated by a stored procedure. The issue is that trailing zeros in
> numeric fields are being truncated. So 1000000.000 becomes 1 and 9500.000
> becomes 95. This issue does not affect string or integer data. As a
> workaround I can convert the data to a string data type in the stored
> procedure and it will be correct. The problem is that this could require
> modifying over a hundred stored procedures. I?d much rather resolve the
> issue. Because the data is correct when the stored procedure is run I
> thought it would be in the ODBC drives but updating to the latest drivers
> available from Sybase did not resolve the issue.
>
> Any ideas would be appreciated.
>
> --jet
>
>