Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved Appeon Server 2016 Number of Digits?

  1. How-to
0
Votes
Undo
  1. Sunki Choi
    Sunki Choi
  2. PowerServer 2020 or older (Obsolete)
  3. Friday, 28 February 2020 08:27 AM UTC

Hi, how are you
We have a problem. Grid Report DW.
You can see all the decimal points in CS when viewing DATA.
However, if you distribute it to Apple server 2016, all the decimal back seats will be cut off.
It appears to be 3.3 => 3.0.
All decimal numbers appear to be zero. Changing the Format property remains the same, and there is no Round,trunate function in SQL.
There are also phenomena that appear to be 2850 => 2500.
AS400 DB2 DB / Powerbuilder12.5

Why doesn't it look the same as C/S?
I really need you to fix it.

Powerserver Debugger - for Chrome?
Appeon workarounds PBL objects need their own work...
Responses (4)
Marco Meoni
Marco Meoni Accepted Answer Pending Moderation
  1. Friday, 28 February 2020 09:45 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi Sunki,

Appeon Web 2016 is EOL since 31/10/2019.

Can you upgrade to Appeon PowerServer 2019 (or even try PowerServer 2020 beta?)

Lots of fixes in there.

Best,

.m

Comment
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Friday, 28 February 2020 14:37 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

I'm currently still on PS2016 web as well, we do not have your decimal problem at all.   We have a large amount of reports and screens where decimal places are critical. We use SQL server, so maybe the setup/difference between that and DB2/AS400 could be the problem.  or something is wrong with your report.  You need to test some of that out. 

I have found bugs in PB that work anyway, that are correctly rejected by PS.   In any case, since 2016 is EOL, you are on your own to figure out a work around.  If you can provide more details of what you are doing and what testing you have done, i can review some of my bug reports to see if it is anything i have seen and what my work arounds have been.

You need to migrate to PS2020 when it comes out.  PS2019 has a bug that prevents us from going to it otherwise we would have moved to that already.   (PS2020 has that bug fixed.)

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 28 February 2020 19:49 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 3

Hi Sunki;

   Did you extend the decimal place support in your PowerServer app(s) from the default value (15) to the higher 28 decimal places?

Note: Screen capture from PS 2019 / 2020

Regards ... Chris

Comment
There are no comments made yet.
Sunki Choi
Sunki Choi Accepted Answer Pending Moderation
  1. Monday, 2 March 2020 00:18 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 4

Thank you from the bottom of my heart for your answer first.
I know PS2016 is EOL.
I've already applied Chris Pollach's answer, but it's not resolved. I also don't have the source, so I can't show you. I'm sorry, but this is a problem with our customers using DB2, and we've modified the query of DW, and we have no choice but to do it as a temporary measure in the future.

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.