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

Resolved Datawindow Release in Export after Migrating

  1. Issue
0
Votes
Undo
  1. Kevin Teynor
    Kevin Teynor
  2. PowerBuilder
  3. Monday, 23 April 2018 18:24 PM UTC

After migrating my source to PB2017, the exports for the datawindows still say "Release 8" (Migrating from PB8).

The only way I see to change that line is to open EVERY datawindow and save them...even without making any actual changes.

Does this need to be done for a valid migration?

  1. DataWindow
  2. Export
  3. Release
  4. Migration
How to activate/deactivate the keyboard functions ...
Is there a Datawindow expression to get actual row...
Responses (1)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 23 April 2018 18:44 PM UTC
  2. PowerBuilder
  3. # 1

Hi Kevin;

   Its been that way since the PowerSoft days. The release number indicates to the run-time system what features that DWO syntax currently supports (feature wise). Once you modify any DWO in any way & save it, the DW Compiler will update the syntax and thus the release number at that time. Otherwise, the DWO's should perform the same in the PB 2017 environment after migration.

HTH

Regards ... Chris

Comment
Kevin Teynor
  1. Kevin Teynor
  2. Monday, 23 April 2018 19:27 PM UTC
Thanks for the quick response Chris!  



Just so I'm clear, do I HAVE to go through the formality of making sure the headers are changed, or can the datawindows remain as-is and still be considered "migrated"?

  1. Helpful
Roland Smith
  1. Roland Smith
  2. Monday, 23 April 2018 20:02 PM UTC
Nope. The app I work on has a few that still say version 6.

  1. Helpful
Kevin Teynor
  1. Kevin Teynor
  2. Monday, 23 April 2018 20:07 PM UTC
Thanks Roland

  1. Helpful
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.