Hello,
I was wondering if anyone knows how to stop PowerBuilder from qualifying an Oracle procedure with its owner in DataWindow Stored Procedure Update properties. We are using a native Oracle driver, not ODBC.
Best regards,
Konstantin
Hello,
I was wondering if anyone knows how to stop PowerBuilder from qualifying an Oracle procedure with its owner in DataWindow Stored Procedure Update properties. We are using a native Oracle driver, not ODBC.
Best regards,
Konstantin
I posted it as a request (bug 3362) and sofar this it what Chris has answered me. I'll try to do that tomorrow, though maybe not for everyone it's easy to get dbo rights on his assigned Oracle user.
Hi Miquel; I believe that the DBO (DB Owner) is added to the DWO's SQL statement when the PB Developer's DBMS login ID is not assigned the DBO role. I have seen this in ASE and SQL Server. By adding the DBO role in those DBMS for me, has always then allowed the PB IDE to drop the prefix. Have you tried this in Oracle? Regards ... Chris
I guess the best thing to do here, is to ask for an improvement / feature request / enhancement to Appeon to achieve the goal of NOT having to edit the dw source code manually all the time.
I'll do that right now.
In the PB IDE, in the connection profile, do you have the powerbuilder catalog owner set to the schema who owns the stored procedure? Do you have synonyms?
Sorry cannot test now myself, as our servers are being maintained.
If not ... do what Juan Alejandro says, though that's something you might have to repeat every time you change something on the dw.
The method that I use, is to edit the Datawindow, by right clicking on the datawindow and selecting the Edit Source option. Then remove the Owner from the Invocation of the Stored Procedure.
It doesn't make a difference.
I've also noted that once you've created the dw, there's no way to "change the datasource". The icon and the menu option is disabled.