1. Johan Tufberg
  2. PowerBuilder
  3. Tuesday, 5 March 2019 15:25 PM UTC

We have recently gone from PowerBuilder 12.6 to PowerBuilder 2017 R3

The method GetSqlSelect() (in DataWindow) has changed its behaviour in a compiled environment. If the datasource in the datawindow isa saved with graphical design then the method GetSqlSelect() does not return the SQL inits original state, the SQL state is converted to all lower case. Example: ”WHERE” is returned as ”where”. ”ORDER BY” is returned as ”order by” and so on. If we run the code in PowerBuilder everything is running as it did previously. 

When compiled we are running with a swedish runtime. We have tried copying PDWE170.DLL and PBOLE170.DLL from the english runtime, but it does not make any difference. PBODB170.INI looks the same as PBOBD126.INI.

Is there anyway to get around this problem so that the GetSqlSelect is returned without being converted to lowercase? 

We are currently facing a huge amount of work to make sure we use Upper() before searching the SQL with Pos() since we have used the functionality and Pos is case-sensitive.

Note: We are running OLE DB to connect to the SQL Server

Regards
Johan Tufberg

Stephan Schröpel Accepted Answer Pending Moderation
  1. Friday, 26 June 2020 10:56 AM UTC
  2. PowerBuilder
  3. # 1

Hi Chris,
thank you for your help. Yes, this could be possible. I had installed my runtime DLLs in an own "shared" directory. And I found another Appeon shared directory with R1 DLLs from an former installation and the first one in the search path.

Best regards from Germany
Stef

Comment
  1. Chris Pollach @Appeon
  2. Friday, 26 June 2020 17:36 PM UTC
Please let us know if that was your issue!
  1. Helpful
There are no comments made yet.
Stephan Schröpel Accepted Answer Pending Moderation
  1. Thursday, 25 June 2020 15:41 PM UTC
  2. PowerBuilder
  3. # 2

Same problem

when running on a machine with PB2019.R2 installed, all works fine. But not in runtime environment. Are there different libraries?

 

Stef

Comment
  1. Chris Pollach @Appeon
  2. Thursday, 25 June 2020 18:24 PM UTC
Hi Stephan;

FWIW: Make sure that you are deploying all the PB 2019 R2 runtime DLL's with you new EXE. Helped a nice lady the other day with a similar issue. She was deploying the EXE into a folder with the PB 2019 GA runtime DLL's already present and *not* the R2 runtime DLL versions. That caused similar issues when run from the EXE but was OK from the IDE. Food for thought. HTH

Regards ... Chris
  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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.