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

Resolved Construct datawindow using SyntaxFormSQL in PowerServer Web

  1. Issue
0
Votes
Undo
  1. Chen Mey Lee
    Chen Mey Lee
  2. PowerServer 2020 or older (Obsolete)
  3. Wednesday, 13 January 2021 13:46 PM UTC

Hi ,

Try to construct datawindow using below syntax but error 10999 return in PowerServer Web, It work fine in PB :-

Web :-

In PB worked fine,

 

 

Failed to parse DataWindow
PowerServer Log4J ?
Responses (5)
Nilotpal Bera
Nilotpal Bera Accepted Answer Pending Moderation
  1. Wednesday, 15 December 2021 12:28 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi ZhaoKai,

 

Greetings!

As per your advise, upgrading all the installations to 1311 resolved the issue.

Also, now there is no need to add temp tables in the select statement.

Working fine without referring any PB catalog tables.

Appreciate your help on this.

 

Thanks,

Nilotpal

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Wednesday, 15 December 2021 16:26 PM UTC
Glad to hear that. Please mark which answer is correct and close this thread. Thanks.
  1. Helpful
There are no comments made yet.
Nilotpal Bera
Nilotpal Bera Accepted Answer Pending Moderation
  1. Monday, 13 December 2021 09:42 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Hi ZhaoKai,

Greetings!
I think the suggested solution was working for PS2020 but it is giving another error with PS2021.
Basically what is happening is that the SyntaxFromSQL function is referring to PB catalog/extended attributes tables which it could not find.
Upon analyzing we found that we have these tables were in another database within the same server. So we copied these tables to the connected database and then the error is resolved but for only those users who belong to dbo group(tables owner is dbo) like developers. But actual end users is still facing issue as the function is trying to refer these tables with transction user id like xyz.pbcatfmt etc.
We also tried adding "PBCatalogOwner='dbo'" to our app's transaction object connection string but no luck.
Kindly have a look into and suggest/advise if it is possible to somehow not to refer these tables by default or if need to refer is there some other way because in our production systems we do not have direct SELECT/UPDATE/INSERT permissions on tables.

Database backend is Sybase ASE 16 connected using ODBC ASE drivers

Error screenshot attached.

You may use any simple sql select statement like mentioned in this thread (no actual table rather table created and referred at runtime)

Thanks in advance and appreciate your help as always!

 
Thanks,
Nilotpal

 

Attachments (1)
catalog.JPG catalog.JPG
Comment
Kai Zhao @Appeon
  1. Kai Zhao @Appeon
  2. Tuesday, 14 December 2021 03:14 AM UTC
Hi Nilotpal,



Thanks for reporting this issue. Sorry that there is no better workaround for this issue, but this issue has been fixed in PowerServer 2021 build 1311, which removes the dependencies on PB catalog/extended attributes tables. Please download and install PowerBuilder 2021 MR Build 1311 to verify it on your side!



You can get the installer from our Downloads portal at https://account.appeon.com/download (login required).



For Installable Cloud apps, please follow the upgrade note to rebuild & deploy your apps after upgrading to PowerBuilder 2021 MR Build 1311.

https://docs.appeon.com/pb2021/release_bulletin_for_pb/Build-1311-Upgrade-Notes.html



Regards,

Kai

  1. Helpful 2
Nilotpal Bera
  1. Nilotpal Bera
  2. Tuesday, 14 December 2021 08:14 AM UTC
Hi ZhaoKai,

Greetings!

Thanks for looking into this.

We have only runtime upgraded to 1311, PB IDE and SnapDevelop still at 1288.

You are correct, maybe this is causing the issue.

We will try and upgrade our installations and verify if the issue is resolved.

Thanks again for your advise.



Thanks,

Nilotpal
  1. Helpful
There are no comments made yet.
Chen Mey Lee
Chen Mey Lee Accepted Answer Pending Moderation
  1. Thursday, 14 January 2021 05:40 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 3

Hi Zhaokai,

Try to add FROM tempdb but the table is not found.  Is there any temp table can use in Sybase database ?

 

Comment
Kai Zhao @Appeon
  1. Kai Zhao @Appeon
  2. Thursday, 14 January 2021 06:27 AM UTC
Hi Chen,



Please try SQL like below.



SELECT ssn_nr= convert(char(30),null),

version= convert(char(30),null) ,

……

FROM (select 1 as mycol) mytemptable



Regards,

Zhaokai
  1. Helpful
Chen Mey Lee
  1. Chen Mey Lee
  2. Thursday, 14 January 2021 06:38 AM UTC
Thanks ZhaoKai, It worked :)

  1. Helpful
Kai Zhao @Appeon
  1. Kai Zhao @Appeon
  2. Thursday, 14 January 2021 06:50 AM UTC
Glad to hear that!
  1. Helpful
There are no comments made yet.
Kai Zhao @Appeon
Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Thursday, 14 January 2021 01:58 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 4

Hi Chen,

The SQL From clause is required on PowerServer. Please use SQL like below to solve the issue.

SELECT ssn_nr= convert(char(30),null),
version= convert(char(30),null) ,
……
FROM t_test

Regards,
Zhaokai

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 13 January 2021 17:03 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 5

Hi Chen Mey;

  What version and build of PowerServer are you using?

  What DBMS version & build are you using?

Regards ... Chris

Comment
Chen Mey Lee
  1. Chen Mey Lee
  2. Thursday, 14 January 2021 05:43 AM UTC
Hi Chris,



I used PB2019 Release 2 and Sybase 12.5
  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.