1. Pierre DETE
  2. PowerBuilder
  3. Thursday, 22 September 2022 17:32 PM UTC


Because of PBCatxxx tables, we are not able to solve getitem invalid datawindow row/column errors.

Our customers used to add  PBCatalogOwner='Technical' (or anything else except 'OP' the schema of our application) to DBParm to avoid some crashes with dynamic datawindows. But with this parameter Oracle database is logging some messages about those tables and some customers noted a performance problems.

PBCatalogOwner are created on schema 'OP'. With PBCatalogOwner='OP' to avoid oracle warning messages, dynamic datawindow with joins are not able to manage column names. So we get some invalid datawindow row/column errors.

We tried to add NoCatlog (1 or Yes) in the pb.ini, we recreate the PBCATxxx tables with the script provided and modified for Oracle.

Nothing is working.

In the background it seems that infomaker is also playing with these tables.

Is there any way to get rid of these tables permanently with powerbuilder?


Thank you for your help









Pierre DETE Accepted Answer Pending Moderation
  1. Friday, 23 September 2022 12:54 PM UTC
  2. PowerBuilder
  3. # 1

I John,

Thank you for your reply.

With DBParm=disablebind=1, staticbind=0, Decimalseparator='.', PBNoCatalog='Yes'

We get the same error as with PBCatalogOwner = 'OP'. In the syntaxe of the dynamic datawindow, Column name's are prefixed by the join name

ie: 'join_name_code' instead of 'code' and we get invalid data row column with a getitemstring on 'code'.


Best regards,




There are no comments made yet.
John Fauss Accepted Answer Pending Moderation
  1. Thursday, 22 September 2022 18:23 PM UTC
  2. PowerBuilder
  3. # 2

Hi, Pierre - 

Have you tried specifying the PBNoCatalog DBParm option in the Transaction Object and/or Database Profile?


Best regards, John

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.