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

Resolved SetTransObject fails with a -1, PB 2017 R3 1880

  1. Issue
0
Votes
Undo
  1. Chris Baldone
    Chris Baldone
  2. PowerBuilder
  3. Monday, 4 March 2019 18:46 PM UTC

Using PowerBuilder 2017 R3 Build 1880.  Nothing .NET, using standard PowerBuilder.

ids_accs = CREATE DataStore

ids_accs.DataObject = "d_users"

ii = ids_accs.SetTransObject(SQLCA)

 

SetTransObject is returning -1 at runtime.  If running in the IDE, SetTransObject works correctly and the application works correctly.  Runtime is a failure b/c of this.

I have seen other post of the same issue using .NET, but not a definate answer.

Is it a Powerbuilder dll or pbd file that is causing this problem?  This is an upgraded application from PB 12.6 and we replaced all of the dll's and the pbdwr126.pbd with the '170' version of the files.  We used the PB tool for packaging up what was needed.

Any help is appreciated.

thx

  1. DataStore
Version of PDFLib in R3?
Recent Word 2010 Update
Accepted Answer
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 4 March 2019 19:46 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi Chris;

  Normally, the -1 on a STO command within a DS is related to a bad DW object. This is normally an issue with the compiled EXE as the developer either forgets to include the DWO(s) via a PBR include or they do not generate a PBD/DLL for each PBL that contains a DWO.

HTH

Regards ... Chris

Comment
Chris Baldone
  1. Chris Baldone
  2. Monday, 4 March 2019 20:00 PM UTC
An older version of a PBD was included in the deliverable instead of the newer. Generating a new one fixed this issue.

thx
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 4 March 2019 20:08 PM UTC
That is Excellent news Chris .. glad that you found the issue!

Have you hugged your DW's today? ;-)

  1. Helpful
There are no comments made yet.
Responses (2)
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Monday, 4 March 2019 19:43 PM UTC
  2. PowerBuilder
  3. # 1

This usually means that the DataWindow object didn't make it into the executable.

You might need to use a .pbr file when deploying the project, specifying any DataWindow objects that are assigned in code.

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.