Bug 6181

PowerBuilder/InfoMaker crash when selecting DropDownDW Style Type 09 September, 2021

Don Olliver
01 March, 2021
Product: PowerBuilder Category: Controls & UI
Version: 2019 R2 Build: 2353
Classification: Issue Publishing: Public
Priority: P3
Status: Closed Reason: RESOLVED
Ken Guo @Appeon 09 September, 2021
#32
Hi Don,

Thanks for your feedback. We are glad that you resolved the issue. 
We will close this ticket first and please feel free to open a new one if you encounter any problems.

Regards,
Ken
Don Olliver 09 September, 2021
#31
(In reply to Ken Guo @Appeon from comment #30)
Hi Don,

Any update?

Regards,
Ken
Hi Ken, We have found a resolution for this problem. Setting 'PowerBuilder Catalog Table Owner' to 'dba' on the Database Profile Setting dialog is the fix; previously it was blank. Thank you for your assistance. You may close this ticket. Regards, Don
Ken Guo @Appeon 01 September, 2021
#30
Hi Don,

Any update?

Regards,
Ken
Ken Guo @Appeon 07 July, 2021
#29
Hi Don,

Thank you very much for your response.
We'll be waiting to hear from you.

Regards,
Ken
Don Olliver 07 July, 2021
#28
(In reply to Ken Guo @Appeon from comment #27)
Hi Don,

Could you provide a virtual machine where this issue can be reproduced for
us to access remotely at any time? A way that the developer can access this
machine via Teamviewer for analysis anytime they need.


Regards,
Ken
Hi Ken, We have asked Corporate IT to set up an environment for your use. I will contact you when it is ready. Regards, Don
Ken Guo @Appeon 05 July, 2021
#27
Hi Don,

Could you provide a virtual machine where this issue can be reproduced for us to access remotely at any time? A way that the developer can access this machine via Teamviewer for analysis anytime they need.


Regards,
Ken
Ken Guo @Appeon 14 May, 2021
#26
Hi Don,

Could you provide a virtual machine where this issue can be reproduced for us to access remotely at any time? A way that the developer can access this machine via Teamviewer for analysis anytime they need.


Regards,
Ken
Don Olliver 13 May, 2021
#25
(In reply to Ken Guo @Appeon from comment #24)
Hi Don,

In our previous meeting, we did reproduce the issue on your machine but we
still haven’t been able to successfully reproduce this issue in our
environment. We still need further analysis and only when we reproduce the
issue locally can the developer find its cause.

Regards,
Ken
Thank you Ken. Do you need anything else from us to facilitate your analysis? Regards, Don
Ken Guo @Appeon 13 May, 2021
#24
Hi Don,

In our previous meeting, we did reproduce the issue on your machine but we still haven’t been able to successfully reproduce this issue in our environment. We still need further analysis and only when we reproduce the issue locally can the developer find its cause.

Regards,
Ken
Don Olliver 12 May, 2021
#23
(In reply to Ken Guo @Appeon from comment #22)
Hi Don,  

I'm just touching base with you about this ticket.  

Did we provide you with enough information to resolve this issue?
Please let us know if there is something else to support you with.  

Regards,
Ken
Hi Ken, We are waiting for Appeon to respond. On 3/15/2021, we demoed the problem in a Teams call and have provided all the information you requested. You were subsequently able to reproduce the issue. Regards, Don
Ken Guo @Appeon 11 May, 2021
#22
Hi Don,  

I'm just touching base with you about this ticket.  

Did we provide you with enough information to resolve this issue?
Please let us know if there is something else to support you with.  

Regards,
Ken
Ken Guo @Appeon 24 March, 2021
#21
Hi Roland,

Thanks for your feedback
However, from the tests we have done so far, Bug 6181 and Bug 6003 are not the same issue.

Regards,
Ken
Roland Smith 23 March, 2021
#20
Is this the same as my bug 6003?
Ken Guo @Appeon 23 March, 2021
#19
Hi Don,

We imported the PBTables you provided into our database and do the test in PB but we can’t reproduce the issue on our side.
I assume that this might be related to the database.
Can you try to verify it via the steps below:
1. Create a new database.
2. Import the PBTables to this new database and then test to see if the issue also exists. 

Regards,
Ken
Don Olliver 16 March, 2021
#18
Bug6181_PBtables.zip (12KB)

(In reply to Ken Guo @Appeon from comment #17)
Hi Don,

We have sent the GoToMeeting link to your account. The link is
https://global.gotomeeting.com/join/200659429.
Sorry that we don’t have a Teams account. If you prefer Teams, you can send
the Teams link for us. Thanks in advance.

Regards,
Ken
Hi Ken, I am happy to hear Rishabh was able to recreate the DropDownDW crash during your meeting. Data for the pbcat* tables is attached. Regards, Don Olliver
Ken Guo @Appeon 12 March, 2021
#17
Hi Don,

We have sent the GoToMeeting link to your account. The link is https://global.gotomeeting.com/join/200659429.
Sorry that we don’t have a Teams account. If you prefer Teams, you can send the Teams link for us. Thanks in advance.

Regards,
Ken
Don Olliver 11 March, 2021
#16
(In reply to Ken Guo @Appeon from comment #15)
Hi Don,

Sure. We would recommend you to make the remote session during our working
time which is 9:00 ~ 17:00 (we are in UTC+8 ) thus we can get immediate help
from the other team if necessary. 

Please let us know when you can make the session.

Regards,
Ken
Hi Ken, Will Tuesday at 9 am your time work for you? If so, please give me a Teams link. We are in UTC-7, so it will be 6 pm Monday for us. Regards, Don
Ken Guo @Appeon 11 March, 2021
#15
Hi Don,

Sure. We would recommend you to make the remote session during our working time which is 9:00 ~ 17:00 (we are in UTC+8 ) thus we can get immediate help from the other team if necessary. 

Please let us know when you can make the session.

Regards,
Ken
Don Olliver 10 March, 2021
#14
(In reply to Ken Guo @Appeon from comment #13)
Hi Don,

I am very sorry that we can't reproduce this issue.
We recommend that you create a new simple case and create two DataWindows
using SQL Select and External respectively.  When you create the Edit Style,
please use these two DataWindows respectively and see if this issue still
occurs and then please let us know the result. If you can still reproduce
the issue, please provide us with this test case, include the PBL, DB Table
Syntax.


Regards,
Ken
Hi Ken, We are still able to recreate the problem at will. Can we schedule a demo with you, perhaps on Microsoft Teams? Thanks, Don
Ken Guo @Appeon 10 March, 2021
#13
Hi Don,

I am very sorry that we can't reproduce this issue.
We recommend that you create a new simple case and create two DataWindows using SQL Select and External respectively.  When you create the Edit Style, please use these two DataWindows respectively and see if this issue still occurs and then please let us know the result. If you can still reproduce the issue, please provide us with this test case, include the PBL, DB Table Syntax.


Regards,
Ken
Don Olliver 04 March, 2021
#12
(In reply to Ken Guo @Appeon from comment #11)
Hi Don,

Thanks for reporting this problem! 
We will be working on analyzing your case. We will keep you posted
on the results here.

I want to ask a question, can you reproduce this problem on other machines?

Regards,
Ken
Hi Ken, Yes, this can be reproduced on other machines. In fact, a client reported the issue when attempting to modify a report using InfoMaker 2019 R2 Build 2353. The same problem occurs in PowerBuilder 2019 R2 Build 2353. Regards, Don
Ken Guo @Appeon 04 March, 2021
#11
Hi Don,

Thanks for reporting this problem! 
We will be working on analyzing your case. We will keep you posted
on the results here.

I want to ask a question, can you reproduce this problem on other machines?

Regards,
Ken
Chris Pollach @Appeon 03 March, 2021
#10
Hi Don;

  Thank you for the Test Case material and also the documentation on the "steps to recreate" the problem crash.

  Unfortunately, I tried creating the Edit Style in both IM2019R2 and PB2018R2 and could not recreate the crash. The DDDW edit style was created & saved each time without any issues. I also tried connecting to SS via ODBC, SNC, & OLE-DB for each DDDW Edit Style creation. Again, no issues using all those DB drivers either.

  Note that I was using the following software for my testing: SS 2019, IM/PB 2019 R2 build 2353, and Windows 20H2 build 19042.804 

  Let's see what the main Support Team has to say on your crashing issue.

Regards ... Chris
Don Olliver 03 March, 2021
#9
Appeon.bug.6181.zip (13KB)

(In reply to Chris Pollach @Appeon from comment #8)
Hi Don;

  I could *not* replicate your issue in my PB2019R2 build 2353 using SS2019
and the SNC driver. However, using my SS2019 and connecting to it with ODBC
I did get a different error when testing the the DDDW Edit Style - but, no
crashing. While OLE-DB, ADO.Net, etc drivers gave me no issues at all for
the for the DDDW edit style assigned in SS.

  What I would suggest now is ...

1) Turn on the SQL trace in your DB Profile
2) Try to assign the Edit Style in the DB Painter
3) Attach the SQL Trace file to this ticket.

  Since you can now recreate the problem crash right from the IDE ... create
a simple test case with "Exact Steps" to recreate the issue and attach these
to this ticket. Include the table DDL and test data that you are using. Many
thanks in advance!

  In the mean-time, I will also now transfer this ticket over to the main
Support Team to see if they have any further suggestions on what might be
causing this crash anomaly.

Regards ... Chris
Hi Chris, I've attached the documentation you requested. Regards, Don
Chris Pollach @Appeon 02 March, 2021
#8
Hi Don;

  I could *not* replicate your issue in my PB2019R2 build 2353 using SS2019 and the SNC driver. However, using my SS2019 and connecting to it with ODBC I did get a different error when testing the the DDDW Edit Style - but, no crashing. While OLE-DB, ADO.Net, etc drivers gave me no issues at all for the for the DDDW edit style assigned in SS.

  What I would suggest now is ...

1) Turn on the SQL trace in your DB Profile
2) Try to assign the Edit Style in the DB Painter
3) Attach the SQL Trace file to this ticket.

  Since you can now recreate the problem crash right from the IDE ... create a simple test case with "Exact Steps" to recreate the issue and attach these to this ticket. Include the table DDL and test data that you are using. Many thanks in advance!

  In the mean-time, I will also now transfer this ticket over to the main Support Team to see if they have any further suggestions on what might be causing this crash anomaly.

Regards ... Chris
Don Olliver 02 March, 2021
#7
(In reply to Chris Pollach @Appeon from comment #6)
Hi Don;

  My next suggestion then would be to create the "Edit Style" from scratch
in the SS DBMS's database. Then make sure that the DDDW works OK not in the
DB Painter but also in a test DWO.

  Once the Edi Style is deemed to be working OK from the DB/DW painters,
then export the PBCATxx tables for that Edit Style and compare the values
for the SS created PBCATxxx tables vs what you are loading in via the
export/import from SQL Anywhere. Hopefully, you will spot the difference.

Regards ... Chris
Hi Chris, We were able to create several new Edit Styles in the Database painter for SQL Server 2017. As soon as we tried to assign any of them to a datawindow column, PB crashed. Regards, Don
Chris Pollach @Appeon 01 March, 2021
#6
Hi Don;

  My next suggestion then would be to create the "Edit Style" from scratch in the SS DBMS's database. Then make sure that the DDDW works OK not in the DB Painter but also in a test DWO.

  Once the Edi Style is deemed to be working OK from the DB/DW painters, then export the PBCATxx tables for that Edit Style and compare the values for the SS created PBCATxxx tables vs what you are loading in via the export/import from SQL Anywhere. Hopefully, you will spot the difference.

Regards ... Chris
Don Olliver 01 March, 2021
#5
(In reply to Chris Pollach @Appeon from comment #4)
Hi Don;

   Thanks Don for confirming that you are using ODBC to connect to SS. By
chance, are the DDDW's that you are trying to use using a Stored Procedure
to get their result sets OR even the parent DWO? 

Regards ... Chris
Hi Chris, The DDDW's result sets are generated by simple SELECT statements. Given a code, they return a code description from a table. Don
Chris Pollach @Appeon 01 March, 2021
#4
Hi Don;

   Thanks Don for confirming that you are using ODBC to connect to SS. By chance, are the DDDW's that you are trying to use using a Stored Procedure to get their result sets OR even the parent DWO? 

Regards ... Chris
Don Olliver 01 March, 2021
#3
PB.SQL.Server.ODBC.Profile.docx (35KB)

(In reply to Chris Pollach @Appeon from comment #2)
Hi Don;

  For SS, what DB Client are you using to connect to the DBMS?
  Also, what settings are you using in the associated DB Profile? 

Regards ... Chris
Hi Chris, We are using ODBC Driver 17 for SQL Server to connect. I have attached screenshots of the PB ODBC Profile settings. Regards, Don
Chris Pollach @Appeon 01 March, 2021
#2
Hi Don;

  For SS, what DB Client are you using to connect to the DBMS?
  Also, what settings are you using in the associated DB Profile? 

Regards ... Chris
Don Olliver 01 March, 2021
#1
sqlserver_script_PBcatcol.zip (17KB)

We run the attached script to populate Datawindow Style Names in SQL Server. In PowerBuilder and InfoMaker 2019 R2 build 2353, the Edit Properties Style Name dropdown causes both applications to crash when a DropDownDW Style Type is selected with an associated data window. 

For example, if I click on the Style Name dropdown and change it to a style name with a style type of DropDownDW, the application crashes. All other style names / style types do not cause a crash. This issue seems to be only occurring in SQL Server databases. I tested the same scenarios in Sybase SQL Anywhere and no crashes occurred. Furthermore, I also compared the tables and columns in SQL Anywhere and SQL Server to make sure the data matches and it does. 

Regards,
Don Olliver
OS:
Windows 10
Platform:
64-bit
Database Type:
Microsoft SQL Server
Database Version:
SQL Server 2017