- Derek Hammonds
- PowerBuilder
- Wednesday, 28 August 2019 02:26 PM UTC
Our large applications use SQL Anywhere 12 and ODBC. We are using Powerbuilder 17 Build 1880.
If you try to put a very simple and very basic query into a datawindow such as...
SELECT "budget"."consumer_id", 0.00 as ohcrap
FROM "budget"
then the resulting datawindow translates the 0.00 as a decimal(0).
Prior to PB 2017 this was always mapped CORRECTLY as a decimal(2) or whatever.
Now, in PB 2017, this is mapped INCORRECTLY as decimal(0). Basically a big integer. No precision.
Editing any existing datawindow that has a literal (real type) coded in this way results in the same BUG: the field is RE-MAPPED incorrectly as a decimal(0).
This is a bug. This is a problem.
Regular database fields are still mapped correctly, FYI.
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.