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

Resolved Datawindow errors in EXE mode

  1. Issue
0
Votes
Undo
  1. Sufyan Maghur
    Sufyan Maghur
  2. PowerBuilder
  3. Friday, 23 September 2022 14:22 PM UTC

I am using PowerBuilder 2021 and have created an EXE package... I am getting an error 900-Invalid SQL Statement with every datawindow when running the EXE... I am not getting the errors when using PoewrBuilder...

I have created the Same EXE using PowerBuilder 2019 R3 the previous version prior to the upgrade of the code and all is well... I have checked all the required PB deployment files and they all exist... Any idea?

  1. DataWindow
  2. Deployment
  3. PowerBuilder (Appeon)
Initialization file is not writeable
PowerClient - Error - Application files are curren...
Responses (6)
Sufyan Maghur
Sufyan Maghur Accepted Answer Pending Moderation
  1. Tuesday, 27 September 2022 18:20 PM UTC
  2. PowerBuilder
  3. # 1

Yes indeed... Hope all is well with you as well smile

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 27 September 2022 18:24 PM UTC
All good here in the Great (soon to be) White North! ;-)
  1. Helpful
There are no comments made yet.
Sufyan Maghur
Sufyan Maghur Accepted Answer Pending Moderation
  1. Tuesday, 27 September 2022 16:19 PM UTC
  2. PowerBuilder
  3. # 2

Hi Chris...

I looked at it again today (Was busy) and I used Appeon PowerBuilder runtime Packager 2021 and made sure my Runtime path is correct C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 21.0.0.1509

All is good now... I forgot to change the runtime path in the OBJECT and didn't rely on the packager (Was used to copying the files I know)...

Thank you for your help

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 27 September 2022 18:17 PM UTC
Hi Sufyan ... That is great news! I am super glad that you found your issue. ;-)

BTW: Long time no see .. I hope that you are doing well.
  1. Helpful
There are no comments made yet.
Sivaprakash BKR
Sivaprakash BKR Accepted Answer Pending Moderation
  1. Monday, 26 September 2022 05:26 AM UTC
  2. PowerBuilder
  3. # 3

Are you using the same (version) runtime files?  If doubtful, copy the xml file created along with the exe to the production folder and point the correct runtime folder in that xml file.

 

Comment
Sufyan Maghur
  1. Sufyan Maghur
  2. Monday, 26 September 2022 12:27 PM UTC
Yes I am and I checked xml and path... will see if there is something I am missing thx
  1. Helpful
There are no comments made yet.
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Friday, 23 September 2022 21:01 PM UTC
  2. PowerBuilder
  3. # 4

Hi, Sufyan - 

Is your application 64-bit?

What database vendor (SQL Server, Oracle, etc.) and database driver (SNC, MSO, ORA, ODB, etc.) does your application use?

If your application is 64-bit, you not only need to use the 64-bit PB runtime DLL's, but you also need a 64-bit version of the database (vendor-supplied) interface DLL's that the PB database drivers call.

Best regards, John

Comment
Sufyan Maghur
  1. Sufyan Maghur
  2. Monday, 26 September 2022 12:28 PM UTC
Will verify thx
  1. Helpful
There are no comments made yet.
Sufyan Maghur
Sufyan Maghur Accepted Answer Pending Moderation
  1. Friday, 23 September 2022 15:02 PM UTC
  2. PowerBuilder
  3. # 5

Thx Chris... Will try, but interestingly when I set it up the trace file is stored in PB 19 directory

C:\Users\maghusu\AppData\Local\Appeon\PowerBuilder 19.0\dbtrace.log

I feel I am missing something pointing to 19 instead of 21

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 27 September 2022 15:47 PM UTC
I wonder if you have the wrong PB runtime installed on the PB App EXE's machine?
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 23 September 2022 14:37 PM UTC
  2. PowerBuilder
  3. # 6

Hi Sufyan;

  If your App EXE draws the DB connection information from a control file (ie: INI), then where it sets the DBMS driver (ie: ODB) - have this setting changed to "TRACE ODB" (where ODB is your current driver). That will then create an SQL Trace. Hopefully, that might expose some more level of DBMS detail as to why you are getting this 900 error.  HTH

Regards ... Chris

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.