Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (6)

Resolved Cannot open the report with PB7

  1. Issue
0
Votes
Undo
  1. Kelvin Doan
    Kelvin Doan
  2. PowerBuilder
  3. Friday, 22 July 2022 17:15 PM UTC

We upgraded our application from PB7 to PB2019R3 . There is a problem with previous reports which saved with PB7, the previous reports with PB7 cannot open on application PB2019 although I did change : 

SQLCA.DBMS = "ASE Adaptive Server Enterprise"
SQLCA.DBParm = "Release='19'"

Only reports saved with 2019 can open.  

Any ideas why it happened ? Thanks 

 

SVN not getting latest
How can I get feedback/debug my Orascript batch fi...
Responses (6)
Kelvin Doan
Kelvin Doan Accepted Answer Pending Moderation
  1. Monday, 25 July 2022 12:16 PM UTC
  2. PowerBuilder
  3. # 1

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.   

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Monday, 25 July 2022 13:03 PM UTC
Hi,

Maybe the problem is related to Unicode. From powerbuilder 10, pb is unicode. If you have reports saved in the database previous to pb10, and if you're using blob fields, maybe you'll have to convert (encode) the reports to ansi once you've retrieved them from the database?

Try retrieving such a blob (in case that's what you have stored) and write it to disk to be able to see what's in them.



Another thing you might want to try is to replace the first line of the code in the reports to include "release 19" instead of something similar to "release 7" (or lower) in the reports' their syntax, before importing them.

regards,

MiguelL
  1. Helpful
There are no comments made yet.
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Friday, 22 July 2022 23:44 PM UTC
  2. PowerBuilder
  3. # 2

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.

Comment
Kelvin Doan
  1. Kelvin Doan
  2. Monday, 25 July 2022 13:27 PM UTC
Thank you Olan. As I clarified that all setup for our reports are saved into database ( from condition , format reports ... ) then we parsed and converse the syntax to Sybase query. From the query, we get report field from tables we need, and made entire report (from report's name to data of report) also saved to database or files (C and DBlibraries syntax) . But when I opened the report on PB application , there is only name of report loaded to the declared text field , other setup conditions for reports are supposed to load to DW before parsing and converting to query , but they don't. Nothing is on DW , it's blank. In addition, when I installed PB2019, PB7 is overwritten. Now I have only PB2019.
  1. Helpful
Roland Smith
  1. Roland Smith
  2. Tuesday, 26 July 2022 14:01 PM UTC
I don't see how installing PB 2019 would overwrite PB7. The install folders and file names are completely different.

As was mentioned by someone else, starting with PB 10 strings are Unicode (2 bytes). PB 7 strings are Ansi (1 byte). If you are using blobs in the database, the older ones will have to be converted to strings like this: String(blobvar, EncodingAnsi!) instead of String(blobvar).
  1. Helpful 1
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 22 July 2022 23:40 PM UTC
  2. PowerBuilder
  3. # 3

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 

Comment
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Friday, 22 July 2022 22:56 PM UTC
  2. PowerBuilder
  3. # 4

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.

 

Comment
Kelvin Doan
  1. Kelvin Doan
  2. Monday, 25 July 2022 13:29 PM UTC
We don't have PSR files, everything of report is saved to database.
  1. Helpful
There are no comments made yet.
Kelvin Doan
Kelvin Doan Accepted Answer Pending Moderation
  1. Friday, 22 July 2022 18:12 PM UTC
  2. PowerBuilder
  3. # 5

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

Comment
John Fauss
  1. John Fauss
  2. Friday, 22 July 2022 19:07 PM UTC
Worth a try.

As a test, in PB7, export a DataWindow to source (.srd file), then in PB 2019, import it. I think I recall hearing about a problem that prevents the successful migration of DW's from PB7 (and earlier) into an Appeon version of PB. If that doesn't work, please post any messages produced during the import.
  1. Helpful
There are no comments made yet.
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Friday, 22 July 2022 17:47 PM UTC
  2. PowerBuilder
  3. # 6

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

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.