We are currently trying out a trial version of PB 2019. We are running against a SQL SERVER 2016 DB. Using the IDE we're able to connect, retrieve and update to the database. When the .EXE is built we can only connect and retrieve from the DB. No error msg is produced. PB is running on Windows 10. SS is running in a 64 bit environment. Wondering if this is some kind of bit rate issue? Or is there something we need on include in the .INI file for DBPARM when we connect to SS? We are using a ODBC connection to the database using the SNC driver that came with Powerbuider.
After some extensive troubleshooting w/Appeon it was discovered if I created .PBD's for each library in the application, versus having a library included with the .EXE, the application runs fine. I have no idea why including a .PBL in the executable would cause the runtime to fail when updating the db???
FWIW: I suspect that your App may not be checking the status of every DB return code after each DML command & logging any non-Zero status. Also, if DW objects are being used, there maybe no DBError event code to trap & log DB issues. Without this type of code, your apps DB exchanges could be failing & you would never know.
I would recheck your App's PowerScript coding around these areas.
If there is no error message, how do you know that update is failing?
Perhaps you can turn on database trace to see what sql commands are being sent.
- Karl Wooley
- Wednesday, 14 August 2019
A PowerBuilder application and the IDE do not connect to the database, they connect to the database interface on the PC it is running on.
The IDE and your app connect to ODBC locally and then ODBC connects to the server database. The bitness of the server has no bearing on the bitness of the ODBC driver.
The bitness of the ODBC driver must match the bitness of the application. The IDE is a 32bit application.
If your application is 32bit, it must use a 32bit ODBC profile and a 64bit application must use a 64bit ODBC profile.
If there was a bitness mismatch, the connect would have failed.
Yes, I'm using 32-bit ODBC driver. I'm curious why the IDE works fine but the .EXE doesn't. They both use the same ODBC driver, yes? Thanks for your assistance, btw!
Have you tried to use the 32 bits ODBC Driver?
The problem might be that your IDE is on 32 bits and the driver you're using is on 64 bits.
Let me know if this works for you.
- Page :
However, you are not allowed to reply to this question.