1. Narayanamoorthy Thangavel
  2. PowerBuilder
  3. Monday, 14 December 2020 12:02 PM UTC

Hi Team,

 

We are facing some problem in PowerBuilder 17 version upgrade. Actually we searched one field value from our application screen but it was fetched the description id instead of description name.

 

Previously it was works fine in the earlier version but it was not working in the PB17 version. There is no logic changed in that. We just upgraded to PB17. Can anyone knows what was the problem in the drop down why it was not showing the description code instead of name.

 

New Version Screenshot for the drop down showing as code.

 

Old Version Screenshot for the drop down showing as code value(Name)

 

 

Note:- The code related to the description name is correct. But we want to display a name of the code.

Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Friday, 18 December 2020 18:23 PM UTC
  2. PowerBuilder
  3. # 1

Hi Narayanamoorthy,

 

Try performing a full build and optimize of each library. That might be able to solve the problem. 

 

Some of you objects could have gotten corrupted. The full build and optimize might be able to help.

 

 

Regards,

Comment
  1. Narayanamoorthy Thangavel
  2. Tuesday, 22 December 2020 04:49 AM UTC
Hi Govinda,



Thank you for you reply. Initially i thought the same solution and i rebuild it complete package along with all the library but it won't help. In our application we have two menu's to change the language . If i clicked the other language menu and it was got updated name details in dropdown and after that it was working. If i just click the language it was loaded fine.
  1. Helpful
There are no comments made yet.
John Fauss Accepted Answer Pending Moderation
  1. Tuesday, 22 December 2020 05:04 AM UTC
  2. PowerBuilder
  3. # 2

Greetings, Narayanamoorthy - 

Can you please post the exported source for primary DataWindow and the impacted Drop-Down DataWindow objects, for both languages, if there are different ones for each language. I'd prefer to have the .srd files zip'd and attached in a new post instead of pasting the exported source, as I'd like to examine them in an editor. Remove the majority of the SQL SELECT statement(s) if you have concerns about security...I want to see the column datatypes, DataWindowChild configuration and other options.

What DBMS are you using, and what SQLCA.DBMS (driver) setting?

Specifically, how are you switching languages? Can you please describe what occurs "under the covers" when this is requested?

Regards, John

Comment
  1. Narayanamoorthy Thangavel
  2. Tuesday, 20 April 2021 05:22 AM UTC
Hi John,



Is there any possibility to get a live session to demonstrate to my issue.?



The problem was there is no change in the code and we just upgraded the powerbuilder from 6.5 to PB2017. But we don't why this issue happened.



Br,

Moorthy



Br,

Moorthy
  1. Helpful
  1. John Fauss
  2. Tuesday, 20 April 2021 14:09 PM UTC
I'm sorry, Moorthy, that is not possible. I'm not employed by Appeon, nor am I a consultant. If you strongly feel you need to work with someone directly, you should maybe consider opening a premium support ticket.



https://www.appeon.com/premium-support.html



Best wishes and good luck!
  1. Helpful
There are no comments made yet.
Matt Balent Accepted Answer Pending Moderation
  1. Tuesday, 20 April 2021 16:00 PM UTC
  2. PowerBuilder
  3. # 3

In going from such an old version I wouldn't be surprised if it were not related to a 'GetChild' datawindow method call.  Have you looked at the script relating to these columns and how they are being populated?

Just a thought...

Comment
  1. Narayanamoorthy Thangavel
  2. Tuesday, 1 June 2021 13:07 PM UTC
Hi,



They are using like this.



gf_filter_codedw_rowstatus( dw_yllapito, "ratkaisutyyppi", "kara.txt", "kuvaus A", s_filtteri )

dw_yllapito.GetChild( "ratkaisutyyppi", dwc_child )
  1. Helpful
  1. mike S
  2. Tuesday, 1 June 2021 16:24 PM UTC
"dw_yllapito.GetChild( "ratkaisutyyppi", dwc_child )"



that shows the getchild. it does not show how you are setting the drop down.



  1. Helpful
There are no comments made yet.
Narayanamoorthy Thangavel Accepted Answer Pending Moderation
  1. Monday, 24 May 2021 07:58 AM UTC
  2. PowerBuilder
  3. # 4

Hi,

 

Appeon will provide the premium support for the above issue to get it resolve? If yes. How should i approach.

 

Br,

Moorthy

Comment
  1. Armeen Mazda @Appeon
  2. Tuesday, 1 June 2021 15:41 PM UTC
Hi Moorthy, For Appeon to help you on this issue you will need to provide us with a reproducible test case. If you can provide us with reproducible test case, please open a premium support ticket using this link: https://www.appeon.com/premiumsupport/newticket
  1. Helpful
There are no comments made yet.
John Fauss Accepted Answer Pending Moderation
  1. Tuesday, 1 June 2021 23:21 PM UTC
  2. PowerBuilder
  3. # 5

My original offer to help you troubleshoot your issue is still valid, but you've not answered any of the questions I posted in my earlier response.

This is a question & answer forum, not a support portal. That's why I am unable to meet with you online The people in the Q&A forum of the Appeon Community try to the best of our abilities to answer the questions that have been posted, but often we need additional information - so we ask follow-up questions. 

It should be obvious that there have been a LOT of changes made to PowerBuilder since version 6.5 that have had a major impact on the product, such as switching from ANSI (single-byte/character) to Unicode (two bytes/character) strings internally, support for newer versions of Windows, support for new versions of RDBMS's, even new database vendors, REST services, etc., so even though YOUR code and/or your DataWindows may not have changed, there has been a lot that has changed under the covers. This may have and evidently has made something in your application work differently than it did previously under version 6.5.

You've still not yet told anyone in this thread what database (vendor, version, character set(s)) you were using under PB 6.5 and what database you are using under PB 2017, so I don't know how you expect anyone to be able to assist you under these circumstances. A test case, example DW's used for the drow-down/child DW and the main/data entry DW would be extremely helpful. regardless of whether you would like the (free) Community to help or the (paid) Appeon Premium Support.

The choice is ultimately yours, but I feel you have not yet fully utilized the expertise and talents available to you here and I encourage you to do so... but you need to meet us halfway.

Comment
  1. Narayanamoorthy Thangavel
  2. Wednesday, 2 June 2021 13:47 PM UTC
Hi John,



I agree your comments.



Actually i am very new to this technology and learning from the scratch.



1. Our current production application is running in PB version 6.5 and it is connected to Oracle 19c . Couple of months back only we upgraded the oracle database from 11g to 19c.

2. Now current application version is PB 6.5 with Oracle 19c and it is working fine with out any problem.

3. So now we are trying to migrate application version 6.5 to PB2017 R3 . All the testing are completed and everything is working fine expect this drop down issue.

4.Can you please let me know how i can take this - (DW's used for the drow-down/child DW and the main/data entry DW )

5. The main language function are written like this.

gv_language.uf_set_language( "ENG" )

gv_language.uf_set_language( "FIN" )



When i am clicking the language button it will change content in datawindow.



6. Data window source code is huge rows are there i could not able to post it here.







  1. Helpful
  1. John Fauss
  2. Thursday, 3 June 2021 01:38 AM UTC
You can select any PB object (window, structure, DataWindow, global function, non-visual user object, etc.) and export the object from the PowerBuilder Library (pbl) where it resides into a stand-along source code file. The file extension of the exported source file will indicate the type of PB object the file contains (.srw = w indow, .srf = f unction, .sru = u ser object, .srd = d atawindow, etc.).

I suggest you export the datawindows involved with this issue into .srd files, then package these files into a zip file. You can add an attachment to any thread reply (but NOT a comment), At the bottom of the thread, underneath where you enter the text of a reply is a button labeled "Upload Files (Maximum size 20MB)". Click on this and you will have the opportunity to attach the zip file you've created. This method is much preferred, as it allows anyone to download and unzip, then inspect the exported source code of these DataWindows, rather than be limited trying read code that has been copied/pasted into a reply.
  1. Helpful
There are no comments made yet.
Sivaprakash BKR Accepted Answer Pending Moderation
  1. Thursday, 3 June 2021 05:28 AM UTC
  2. PowerBuilder
  3. # 6

1.  Can u check whether the data column and display column of the dropdown datawindow haven't got modified between 6.5 and 2017.

2.  Whether the data (code value(name) could be read for the code that's get displayed from a test datawindow.  aka whether data exists in the database for the code.

my 2 cents

Happiness Always
BKR Sivaprakash

 

Comment
  1. Narayanamoorthy Thangavel
  2. Thursday, 3 June 2021 05:52 AM UTC
Hi Siva,



1. You mean like in the data window for the specified field value . ( In the properties - Position value have to check ?)

2. Yes in the data base for the specified code description updated fine and retrieved from there.
  1. Helpful
  1. Sivaprakash BKR
  2. Friday, 4 June 2021 08:01 AM UTC
1. In the Edit properties of the concerned field, style will be DropDownDW, at the bottom, datacolumn and displaycolumn will be there, below Datawindow column. See whether anything changed between old dw and upgraded dw.



1a. See whether the dropdown datawindow list all values [when clicked the arrow]. Just to see whether all values of the dropdown datawindow is retrieved or not.



If not retrieved, you could check the query that retrieves the data. Probably, some comments may in the query may not work as expected with newer driver(s).

  1. Helpful
There are no comments made yet.
Narayanamoorthy Thangavel Accepted Answer Pending Moderation
  1. Thursday, 3 June 2021 05:42 AM UTC
  2. PowerBuilder
  3. # 7

Hi John,

 

Both window and data window file attached here.

Attachments (1)
Comment
  1. John Fauss
  2. Friday, 4 June 2021 01:36 AM UTC
I have the objects. What are the names of the column or columns in the DataWindow which do not work? Can you please post the exported source for the drop-down datawindow(s) used by these columns?

What is the name of the DataWindow Control in the window?
  1. Helpful
There are no comments made yet.
Narayanamoorthy Thangavel Accepted Answer Pending Moderation
  1. Friday, 4 June 2021 09:59 AM UTC
  2. PowerBuilder
  3. # 8

Hi,

Below are the fileds getting updated code instead description.

Ratkaisu - ratkaisutyyppi
Tot.tapa - liittymatyyppi
Tap.laji- tapahtumalaji
Resepti - reseptitunnus

 

What is the name of the DataWindow Control in the window?  --->d_tilliittyma

 

Can you please post the exported source for the drop-down datawindow(s) used by these columns? --> Can you tell me how i can take the specific columns source details from datawindow?

 

For reference image.

 

Comment
There are no comments made yet.
John Fauss Accepted Answer Pending Moderation
  1. Saturday, 5 June 2021 03:45 AM UTC
  2. PowerBuilder
  3. # 9

From examination of the exported datawindow source code, I see the following:

Column id 96: ratkaisutyyppi  char(8)
DDDW name: d_pop_koodi  DisplayColumn: kuvaus  DataColumn: poptunnus  DDDW.limit = 0

Column id 16: liittymatyyppi  char(8)
DDDW name: d_pop_koodi  DisplayColumn: kuvaus  DataColumn: poptunnus  DDDW.limit = 40

Column id 11: taphtunalaji  char(8)
DDDW name: d_pop_koodi  DisplayColumn: kuvaus  DataColumn: poptunnus  DDDW.limit = 40

Column id 26: resepitunnus  char(8)
DDDW name: d_muko_koodi  DisplayColumn: nimi  DataColumn:  koodi  DDDW.limit = 40

Since I do not have the source for d_pop_koodi and d_muko_koodi, I can only assume the columns identified as the DataColumn are also defined as char(8). That is one item I suggest needs to be checked.

I'm not sure why the dddw.limit is not the same for these columns. Another thing you could experiment with.

I suspect there may be a problem with the changes being made at execution time to switch languages. Since you have functions in global objects dynamically making significant changes to the main datawindow, I suggest you temporarily add a command button to the window that extracts and displays the dddw.displaycolumn and dddw.datacolumn properties of each of these four column objects... This can be done via dot notation:

String ls_displaycolumn, ls_datacolumn
ls_displaycolumn = d_tillittyma.Object.ratkaisutyyppi.dddw.displaycolumn
ls_datacolumn = d_tillittyma.Object.ratkaisutyyppi.dddw.datacolumn

or via Describe:

String ls_displaycolumn, ls_datacolumn
ls_displaycolumn = d_tillittyma.Describe("ratkaisutyyppi.dddw.displaycolumn")
ls_datacolumn = d_tillittyma.Describe("ratkaisutyyppi.dddw.datacolumn")

Then display these values (along with the column name) via MessageBox. I'm not familiar how this app works, but if possible, check these values before and again after switching languages.

The only other suggestion I have is to temporarily disable the dynamic property changes to these columns, if possible, to see if the errant behavior clears up. That might indicate or give a clue where the issue lies.

 

Comment
  1. Narayanamoorthy Thangavel
  2. Monday, 7 June 2021 12:33 PM UTC
Hi,



Since I do not have the source for d_pop_koodi and d_muko_koodi, I can only assume the columns identified as the DataColumn are also defined as char(8). That is one item I suggest needs to be checked.--->How do i take source for the d_pop_koodi and d_muko_kood .



I'm not sure why the dddw.limit is not the same for these columns. Another thing you could experiment with. ---> Current production version 6.5 it was working fine for these value columns.



I suspect there may be a problem with the changes being made at execution time to switch languages. Since you have functions in global objects dynamically making significant changes to the main datawindow, ---> If i login the application with one language and moving to the problem window i am facing the problem and if i changed to other language and it is working. Then again if i came back to the original login language its working fine. So i thought it should not be language change problem . Do i need to clear any buffer for the particular datawindow field?

  1. Helpful
  1. John Fauss
  2. Wednesday, 9 June 2021 01:42 AM UTC
I don't need to see the exported source for the d_pop_koodi and d_muko_koodi DataWiundows, but if I did, you would export these objects, producing d_pop_koodi.srd and d_muko_koodi.srd files, put them in a zip file and attach the zip file in a reply just as you did earlier.

I understand your frustration with this issue, but stating repeatedly that this code works in PB 6.5 is largely irrelevant... what's important is that the code does NOT work now, so I suggest you focus your efforts on diagnosing the problem.

Unfortunately, given the complexity of the application/code, I'm limited as the amount of help I can offer. I've described in general terms a possible way for you to perform further investigation, but that is only a suggestion. If you're unable or unwilling to do what it takes to diagnose the issue, you should consider opening a premium support ticket with Appeon or bring in an experienced consultant. I wish you the best of luck.
  1. Helpful
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.