1. Richard Carrier
  2. PowerBuilder
  3. Wednesday, 3 April 2019 21:29 PM UTC

In our app, using the latest build, the OpenwithParm passing a string parm has not been fixes. PowerObject works but not the string.

Anyone else detect this ?

Thanks

Richard

Kevin Ridley Accepted Answer Pending Moderation
  1. Thursday, 4 April 2019 15:17 PM UTC
  2. PowerBuilder
  3. # 1

Hey Richard,

 Glad to hear you guys are longtime PB enthusiasts.  Definitely wasn't saying that you guys didn't know how to get the stringparm, I was just trying to say that something else may be happening now that is messing with the value.  Often times with newer versions of PB, the timing of events can change, so the message object stringparm may have been fine where you are accessing it in the prior version, but now something may be stepping on it.  I attached a simple quick app I wrote that uses the message stringparm and opensheetwithparm and it is working.  I would definitely check any ancestor code in the sheet's open event to see what else may be happening before you access the message.stringparm.

 

Good luck,

Kevin

Attachments (1)
Comment
  1. Richard Carrier
  2. Thursday, 4 April 2019 15:22 PM UTC
Thank you. It does sound like it must be on our end which would actually be good news. Thank You!
  1. Helpful
  1. Kevin Ridley
  2. Friday, 5 April 2019 15:20 PM UTC
You're welcome. When you find it, be sure to post back here and tag it as the solution so if anyone else is having a similar problem they can try what you found.
  1. Helpful
There are no comments made yet.
Kevin Ridley Accepted Answer Pending Moderation
  1. Thursday, 4 April 2019 13:03 PM UTC
  2. PowerBuilder
  3. # 2

When you say you are using the latest build I assume you are using PB2017 R3.  I've created a bunch of POC type apps in PB2017 R3 that use the message.stringparm with no issues, so I don't think it's a bug.  Can you post your code?  There's probably a good chance that you have other code that's happening before you try to get the stringparm.  Try to be sure that getting the stringparm from the message is the first thing that happens on the window you are opening.  Check that there is not some ancestor code happening that is messing with the message object.  You can always try to override the ancestor code in the window open, then call super after you get the message.stringparm.

 

KR

Comment
  1. Richard Carrier
  2. Thursday, 4 April 2019 14:49 PM UTC
I meant to say Opensheetwithparm. I think the openwithparm is working. We appreciate your feedback.

FYI my group had been using Powerbuilder since version 2.0 in 1993 and so we are familiar with how to get the parms.



Let me know if the Opensheetwithparm works for you. I would really like to know.

Thanks

Richard
  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.