-
Roy Bungert
- PowerBuilder
- Thursday, 8 February 2018 08:11 AM UTC
Known issues with DB Name of computed fields
If a named computed field is added in DataSource, its DB Name will be compute_4-digit-number, rather than the name declared in the computed field statement. For example, if you execute the following SQL statement to add a column after creating the DataWindow:
SELECT column_a FROM table_b WHERE table_b.id = table_c.id AS example_column;
In PowerBuilder 2017, the DB Name is example_column, while in PowerBuilder 2017 R2, the DB Name is custom_4-digit-number.
The changed Naming of computed columns in DataWindows Destroy the DataWindow GUI
Our problem:
From my point of view PB2017R2 is totaly unusable for projects (with DWs) which are created before PB2017R2.
As a result of this known issue / bug we have the following problem:
We have a DW (from PB2017R1) with computed fields defined in the SQL.
If we want to change (or delete) one of the these computed colums in the SQL, all computed fields (from the SQL) are delete from the dw and added at other positions. In Grid style, all headings, formats etc are lost. So, a our reports can't be used anymore.
Is this a general problem or does it depend of certain settings (We use SQL Anywhere)?
I hope there is a workarounds. I guess that this is a bigger problem for Appeon. If it wouldn't be a big one, they would have fixed it, instead of documenting it in the "Known issue" list.
I hope for help
Roy
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.