Phenomenon:

When you add the

StripParmNames='Yes'

Parameter into the DBPARM and, at the same time, add the

PBNewSPInvocation='Yes'

parameter, the the first one doesn't work.

 

Scenario:

If you combine both the

StripParmNames='Yes'

and the

PBNewSPInvocation='Yes'

into the same DBPARM like this:

ConnectString='DSN=Sxx_2;UID=MXX;PWD=XX;connectionname=DBNAMEXYZ',Block=1, DisableBind=1,ConnectOption='SQL_DRIVER_CONNECT,SQL_DRIVER_NOPROMPT',StripParmNames='Yes',PBNewSPInvocation='Yes'

then the

StripParmNames='Yes'

setting doesn't take effect.

 

Workaround:

1.- Go to: \Appeon\Shared\PowerBuilder

2.- Open pbodb170.ini

3.- Add a new line (PBNewSPInvocation='Yes') under the category: [Adaptive Server Anywhere] or to the corresponding Database Section depending on your DBMS.

It should look something like this:

[Adaptive Server Anywhere]
PBSyntax='WATCOM50_SYNTAX'
PBDateTime='STANDARD_DATETIME'
PBFunctions='ASA_FUNCTIONS'
PBDefaultValues='autoincrement,current date,current publisher,current time,current timestamp,current user,last user,sqlcode,sqlstate,timestamp,null,user'
PBDefaultCreate='YES'
PBDefaultAlter='YES'
PBDefaultExpressions='YES'
DelimitIdentifier='YES'
PBDateTimeInvalidInSearch='NO'
PBTimeInvalidInSearch='YES'
PBQualifierIsOwner='NO'
PBSpecialDataTypes='WATCOM_SPECIALDATATYPES'
IdentifierQuoteChar='"'
PBSystemOwner='sys,dbo,sa_debug,rs_systabgroup'
PBUseProcOwner='YES'
SQLSrvrTSName='YES'
SQLSrvrTSQuote='YES'
SQLSrvrTSDelimit='YES'
ForeignKeyDeleteRule='Disallow if Dependent Rows Exist (RESTRICT),Delete any Dependent Rows (CASCADE),Set Dependent Columns to NULL (SET NULL)'
TableListType='GLOBAL TEMPORARY'
PBNewSPInvocation='Yes'

4.- Save the file.

5.- Remove the PBNewSPInvocation='Yes' option from your DBParm.

6.- Restart PowerBuilder.

  • Up
    1
  • Down
    0