Hi, Kelvin - 

I suspect the "Release=19" you've specified in the DBParm setting is not correct:

https://docs.appeon.com/pb2021/connection_reference/Database_parameters_and_supported_database_interfaces.html#Release

This value is NOT the PB version, nor is it the ASE version. Rather (as the documentation explains), this denotes the version of the Sybase Open Client software available on the machine. The latest value listed is 15.5

I suggest you first create and configure a Database Profile within the PB IDE that allows you to use the Database Painter in PB successfully. Then you can take the settings used in the working DB profile to set the Transaction object properties.

Best regards, John

Hi John, 

Thank you for your response.  You are correct. I did change the previous release from 16 to 19 on the code , just expect the reports can open. The number 16 is coming from the syntax of DB profile. On my connection of Database Profile shows release from 15, 15.5 and 16 . I picked release 16. Now I change release to 15.5 as you suggested , the reports still cannot open. 

Thank you, Kelvin

When you say 'Only reports saved with 2019 can open', are you talking about PSR files?

There was a PSR file format change in PB8 which would prevent a PB 2019 PSR from being opened in PB7.

Hi Kelvin;

 A PSR file contains the DataWindow source code plus data in a proprietary format. Since the DWO source is included, the format is in the version of PB that the PSR was generated in. Thus, the PSR is only valid to be read in the same version of PB that it was created in.

Regards..  Chris 

If possible, I'd suggest you export the reports from PB7, then IMPORT those reports into a new PBL in your 2019R3 application. Then regenerate them.

That seems to be the cleanest and easiest way of migrating the reports.

Thank you for your response. I would like to clarify the problem as below: 

Our reports are setup on database (Sybase 16) that meant from reports' condition setup (syntax) , report type setup. etc... are saved in database, no PSR . The reason for this is : long time ago, we had reports with syntax of very old language (similar like Cobol), so we built PB application and we want the customers are familiar with the syntax when they use application, so we saved everything to database, then we have to parse and converse the old syntax to the query to execute. When we upgraded the PB7 to PB2019, all the setup for reports are not loaded to DW for reports saved with PB7, except those reports saved with PB2019.