- Pierre DETE
- PowerBuilder
- Thursday, 22 September 2022 05:32 PM UTC
Hello,
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
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.