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

Resolved How to troubleshoot PB Datawindow import error

  1. Issue
0
Votes
Undo
  1. dale walker
    dale walker
  2. PowerBuilder
  3. Thursday, 7 February 2019 23:00 PM UTC

Looking for some troubleshooting suggestions.   I'm receiving a datawindow error trying to import a SRD source file.   The reported row and column do not match the actual SRD source file.   Not even an off by a couple rows close.  

The reported apparent row/column is an embedded SQL statement, which I've verified is syntaxically correct via  SQL Developer and TOAD.

For background, leading up to the error, 1) performed datawindow export, 2) manually changed "[short date]" to "[shortdate]" in a number of Format tags, 3) tried to re-import, received error below

 

 

Environment: PB 2017 R3, Windows 10 x64

  1. DataWindow
  2. Error
  3. Import
  4. PowerBuilder (Appeon)
error on install 1880
BitBucket Git Server - Anyone Out There?
Responses (4)
dale walker
dale walker Accepted Answer Pending Moderation
  1. Friday, 8 February 2019 20:03 PM UTC
  2. PowerBuilder
  3. # 1

thanks all.  I ended up where Brad commented and was able to import an older SRD with corrections

Found an older version of the SRD, ran a compare and added the new bits to the old SRD, then re-imported.  All is good again.  The row/column info from the PB import parser is still a bit of mystery to me.   Counting with or without header and embedded SQL as 1, the reported parse error location still didn't make any sense.

Comment
Brad Mettee
  1. Brad Mettee
  2. Saturday, 9 February 2019 14:25 PM UTC
Armeen,

As an enhancement, it might be helpful to have the text causing the parsing error in the error message. Any amount of additional info to nail down an error location would be helpful.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Monday, 11 February 2019 19:00 PM UTC
Please send an email to product@appeon.com to suggest this enhancement. Thanks.
  1. Helpful
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Friday, 8 February 2019 19:17 PM UTC
  2. PowerBuilder
  3. # 2

I made another comment but it was mistaken. The forum doesn't allow deleting a post.

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 8 February 2019 21:45 PM UTC
Comments can be deleted. Only answers cannot, but you could always edit the answer.
  1. Helpful
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Friday, 8 February 2019 19:17 PM UTC
  2. PowerBuilder
  3. # 3

Line 1 is where it says:  release 17.0;

Count down from there. 

 

Comment
Brad Mettee
  1. Brad Mettee
  2. Saturday, 9 February 2019 14:23 PM UTC
Just to clarify, the first line of an object that's exported to a file is "$PBExportHeader$dw_whatever.srd". This is the line that's not included in the line count.
  1. Helpful
There are no comments made yet.
Brad Mettee
Brad Mettee Accepted Answer Pending Moderation
  1. Friday, 8 February 2019 15:16 PM UTC
  2. PowerBuilder
  3. # 4

If you have a backup of your PBL, you're going to be fine. Rename the bad copy of the datawindow so you can use it as reference. Export the datawindow from the backup, see if you can import it into live. If so, compare the working srd with the non-working srd to see what's actually different. 

As far as line numbers go, I'm almost positive that the select statement (line starts with " retrieve=") gets collapsed into a single line and continues from there. Line number will then be off by one (I think line 1 gets ignored). Column number may not match up either since the parser is looking for specific text markers, and if something is missing or improperly spelled, the actual problem will be prior to the shown column number.

Hope this helps.

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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.