Hello. Thank you for your response. However, I already do these steps in past (for another kind of problems), and didn't can solve it. Next I include some additional data:
The application was migrated from the IDE Powerbuilder 9 to Powerbuilder 2017, taking into account that the database connection driver was changed to SNC Native Client, having to modify the following parameters in order to maintain functionality. Modified connection properties:
* DBMS: SNC SQL Native Client (OLE DB)
* Provider = 'SQLNCLI11
* OptSelectBlob = 1
* BinTxtBlob = 1
* DateFormat = \ dd / mm / yyyy \
* DateTimeFormat = \ dd / mm / yyyy hh: mm: ss.fff \
* TimeFormat = hh: mm: ss.fff \
The following statements are executed before making the connection using the transaction object
* EXECUTE IMMEDIATE "SET ANSI_WARNINGS OFF;" USING SQLCA;
* EXECUTE IMMEDIATE "SET ANSI_NULLS OFF;" USING SQLCA;
In the majority of cases it happens executing the compiled application, when opening a report of a datawindow, and it occurs during the reading of information (for which I assume that it is something of the interaction with the database).
BTW: sorry for the redaction, i'm from Argentina and have a medium/low english handle.
May I suggest ....
1) OptSelectBlob is not supported by SNC
2) BinTxtBlob=1 means non-Unicode data. Whereas PB2017Rx is fully Unicode
3) Make sure that all DBMS interactions check the DB return status code(s).
4) Not sure why your App is turning off ANSI_Warnings and NULLs.
Try commenting these "SET" commands out as its not common a practice.
5) Try tracing your app's EXE by adding the " /pbtrace" to the EXE start-up
6) Try adding in an SQL trace ... (SQLCA.DBMS = "TRACE SNC")
7) Review your App's code for Unicode compliance. PB9 was ANSI based
- ANSI defined external functions => Unicode
- ANSI based PowerScript commands => Unicode
8) DB Date formats should always be CCYY-MM-DD internally
9) DB DateTime formats should always be CCYY-MM-DD HH:MM:SS:FFF internally
Also... did you run the PB 2019 "Migration Assistant" on your PB 9 App source before migration to see if it logged any PB 9 features that need to be cleaned up for PB 2017?
HTH
Regards ... Chris