Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Select error: Data-conversion resulted in overflow

717 views
Skip to first unread message

Herman Mol

unread,
Nov 25, 1999, 3:00:00 AM11/25/99
to
Hi,

We have migrated an app from PB4 to PB6.5
In both cases the database is MS SQL Server 6.5 sp5, native connection.

In PB4 all is OK, but with PB6.5.1 we get the above error.

Has anyone any clues?

Thanks.

Herman Mol

Dennis_Nickels

unread,
Nov 25, 1999, 3:00:00 AM11/25/99
to
Check that the selected data matches the receiving var on type and size.
For example are you selecting a long into an integer?

Herman Mol

unread,
Nov 28, 1999, 3:00:00 AM11/28/99
to
Case solved!

It appeared that in some datawindows a kolom was defined as char(60), but
it's definition on the database is varchar(255).
If the datalength was > 60, the error occurred. One of the users of the app
could tell me enough details and with the background info from this
newsgroup I was able to narrow the problem.

Finally I used a PB-app to scan and report all (>700) datawindows and their
column's coltypes.

Appearantly PB4 was less critical than PB6.... :-\

Thanks for the input!

Herman.


Herman Mol heeft geschreven in bericht ...

Herman Mol

unread,
Nov 28, 1999, 3:00:00 AM11/28/99
to

Jim O'Neil [Sybase]

unread,
Nov 29, 1999, 3:00:00 AM11/29/99
to
Herman Mol wrote:

> Case solved!
>
> It appeared that in some datawindows a kolom was defined as char(60), but
> it's definition on the database is varchar(255).
> If the datalength was > 60, the error occurred. One of the users of the app
> could tell me enough details and with the background info from this
> newsgroup I was able to narrow the problem.
>
> Finally I used a PB-app to scan and report all (>700) datawindows and their
> column's coltypes.
>
> Appearantly PB4 was less critical than PB6.... :-\
>
> Thanks for the input!
>
> Herman.
>

Actually, PB4 was (by default) less efficient than PB6. In PowerBuilder 4 and
prior, the default behavior was to re-describe datawindows for each retrieval
to allow for adjustments such as you ran into. In PowerBuilder 5, the default
behavior was switched to NOT do this, as it it is a relatively expensive
operation. You can get the old behavior by setting StaticBind=0; however, the
best resolution is to fix it at the source as you did.

--
Jim O'Neil
Senior Technical Support Engineer
Sybase, Inc

0 new messages