1. mike S
  2. PowerBuilder
  3. Tuesday, 8 February 2022 21:19 PM UTC

PB2019R3 BUILD 2728

Getting a couple of sql server errors using 64 bit PB and ODBC.  32bit PB no problems.  I didn't get this with PB 2017R3 64 bit.  

 

The first one is caused by running a datawindow with a string argument:

Select Error: SQLSTATE = 22005 [Microsoft][ODBC SQL Server Driver]Invalid character value for cast specification

 WHERE tab_cd = :reportcode

 

getting rid of the argment in the sql 'fixes' the problem:

WHERE tab_cd = 'BALSH'  

 

the 2nd error: 

Select Error: SQLSTATE = S1C00
[Microsoft][ODBC SQL Server Driver]Optional feature not implemented

have not tracked this one down yet.

 

 

these are set in my connection string.  this is regular sql (not stored procedure, stored procedures work fine)

CallEscape='No'

StripParmNames='Yes'

 

 

anyone have any ideas?

 

Accepted Answer
mike S Accepted Answer Pending Moderation
  1. Tuesday, 8 February 2022 21:30 PM UTC
  2. PowerBuilder
  3. # Permalink

DisableBind=1

thanks don:  https://community.appeon.com/index.php/qna/q-a/sql-server-errors-after-pb-2017-r2-migration

Comment
  1. Miguel Leeuwe
  2. Tuesday, 8 February 2022 23:04 PM UTC
I'm using PB 2019 R3 with an Oracle 19c database and an Oracle 19c client (32 bit). Previously, we used a 12c and 11g database with their appropiate clients.

When we started to use the 19c client, I've seen some weird errors (that didn't 'always' happen. Me too I discoverd that setting Disablebind=1 solves all of these problems. Something seems off.

regards
  1. Helpful
  1. Miguel Leeuwe
  2. Tuesday, 8 February 2022 23:05 PM UTC
(that was using the Oracle native clients btw).
  1. Helpful
There are no comments made yet.


There are replies in this question but you are not allowed to view the replies from this question.