1. Minogue Susan
  2. PowerBuilder
  3. Thursday, 5 March 2020 14:59 PM UTC

Hi Team, 

We are using PB 2017 R3 Build 1858. We are facing issue in changing axis value properties of minimum and maximum values. When we try to change the values it again back to existing one. 

For example: In minimum we have value 4000 and in maximum 9000 we would like to change it to 4500 - 9500 but it didn't change. Whenever we tried, it again go back to existing one. 

Please advise.

Thanking you,

Anil

David Peace Accepted Answer Pending Moderation
  1. Thursday, 5 March 2020 15:10 PM UTC
  2. PowerBuilder
  3. # 1

Hi

I have not tried it, but can you edit the values using Edit Source?

Regards

David

Comment
  1. Olan Knight
  2. Monday, 9 March 2020 22:08 PM UTC
It has been my experience that once a crosstab or a graph control is created and saved, it is FIXED.



I'm sure you have already tried passing in the VALUES as parameters, and I'm guessing that failed.



It might be possible to get the DW syntax, make your VALUE changes inthe syntax directly, and then re-import the DW into the PBL. That might work for you where dot notation and parameters have failed.



Olan
  1. Helpful
  1. Konrad Kaltenbach
  2. Wednesday, 17 November 2021 08:53 AM UTC
Hi,

even this fails:

I introduced two Computed Field controls y_max_plus and y_min_minus.

Afterwards I used menu item "Edit Source" and changed the source of the DataWindow in the following way:

"values.maximumvalue="y_max_plus" values.minimumvalue="y_min_minus"".

I exported the DW, deleted it, closed PowerBuilder (Professional Edition Version 2019 R2 Build 2353), opened it again and reimported the DW.

But whenever savíng the DW again in the painter (!), values.maximumvalue="100" values.minimumvalue="0" are set again.

Konrad
  1. Helpful
  1. Olan Knight
  2. Thursday, 18 November 2021 07:53 AM UTC
You're hosed. Rewrite the dw.

  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 6 March 2020 16:39 PM UTC
  2. PowerBuilder
  3. # 2

Hi Sadananda;

   It almost sounds like the DWO is not being saved because its associated PBL Library (or associated folder) is write protected.

Regards ... Chris

Comment
  1. Minogue Susan
  2. Monday, 9 March 2020 13:50 PM UTC
Hi Chris,



It is not write protected because we can make changes for other issues where as only for graph axis properties the values are not getting changed. I was working fine few days ago but now the valued are not getting modified and it is not write protected.



Thanks.
  1. Helpful
There are no comments made yet.
John Fauss Accepted Answer Pending Moderation
  1. Monday, 9 March 2020 20:06 PM UTC
  2. PowerBuilder
  3. # 3

Hi, Sadananda -

I don't believe I've ever used a DataWindow graph outside of a classroom setting. However, I see in the PB Help that the Axis MinimumValue and MaximumValue properties can be an expression.

As a possible workaround, maybe add four numeric retrieval argument values to the DataWindow (not to be used in the data retrieval) named, say as "XAxisMin", "XAxisMax", "YAxisMin" & "YAxisMax". Then via Edit Source if you have to, replace each of these hard-coded values with an expression that is simply the appropriate retrieval argument value, for example:

   ... MaximumValue="4000~tXAxisMin" ...

The value preceding the tab character is the property's default value. The expression comes after the tab character.

This should allow you to dynamically set the axis Min/Max values via retrieval arguments. Maybe it's not an ideal solution, but I hope it helps!

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 10 March 2020 14:25 PM UTC
  2. PowerBuilder
  3. # 4

Hi Sadananda;

   Can you export this DWO source code and attach it to this thread for us to look at?

Regards ... Chris

Comment
There are no comments made yet.
Brad Mettee Accepted Answer Pending Moderation
  1. Wednesday, 17 November 2021 14:58 PM UTC
  2. PowerBuilder
  3. # 5

It sounds like the PBL is either corrupted itself, or the DW object is.

Export to DW to file, delete it from the pbl, optimize pbl, import DW from .srd. See if you can make changes now. If not, there's something fundamentally wrong with that datawindow and you should try to rebuild it from scratch and see if it can be changed afterwards.

 

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.