1. Rick Hiebert
  2. PowerBuilder
  3. Wednesday, 13 December 2023 19:14 PM UTC
Using the LibraryImport powerscript function. The code has worked for over 15 years and we have not made any changes to the code in years. Just upgraded from PB2021 to PB2022. The code continues to work in the IDE, but once compiled it does not work. The dw definitions in the database are PB2017. They are created for a second application that is still in PB2017 so can not be changed.
Rick Hiebert Accepted Answer Pending Moderation
  1. Thursday, 14 December 2023 13:47 PM UTC
  2. PowerBuilder
  3. # 1
Hi Chris,

1) The DWO syntax is saved in a text column.
2) We are using a datawindow to retrieve the syntax.
3) Yes, DWO syntax header is stating "release 17;"
4) We do not create an SRD file before using the LibraryImport function. 

Thanks, Rick
Comment
  1. Chris Pollach @Appeon
  2. Thursday, 14 December 2023 20:40 PM UTC
Hi Rick;

I would then suggest the following .... Use a SelectBlob command to read the DWO source and see if that works.

My thought here is that the DWO Retrieve() is somehow not getting all the DWO Source or the Source is coming across corrupted.

Just a guess at this point. Food for thought

Regards ... Chris

  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 13 December 2023 23:13 PM UTC
  2. PowerBuilder
  3. # 2

Hi Rick;

  Can you tell us ...

  1. What type of DB Column is the DWO source saved into?
  2. Are you performing a SelectBlob command to get the DWO source out of the DB?
  3. Is the DWO source (SRD file) header stating "release 17;"?
  4. Is the saved .SRD file from the DB before the Libraryimport command being saved in UTF-16LE format?

Regards .. Chris

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.