StripParmNames=’Yes’ is not working when PBNewSPInvocation=’Yes’
is used in the DBparm
Phenomenon
When you add the StripParmNames=’Yes’ parameter into the DBparm
and, at the same time, add the PBNewSPInvocation=’Yes’ parameter, the
first one doesn’t work.
Scenario
If you combine both the StripParmNames=’Yes’ and the
PBNewSPInvocation=’Yes’ into the same DBparm like this:
|
1 |
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: AppeonSharedPowerBuilder
2. Open pbodb220.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 like this:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 |
[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.
Document get from Powerbuilder help
Thank you for watching.
Subscribe
Login
0 Comments
Oldest