1. David Vasconcelos
  2. PowerBuilder
  3. Friday, 25 May 2018 14:04 PM UTC

Works in PB2017 but not working once converted to Appeon Web.  Anyone encountered this or have a work around?

Environment Win 10 64bit, PB 2017 R1

Accepted Answer
Michael Kramer Accepted Answer Pending Moderation
  1. Sunday, 27 May 2018 10:04 AM UTC
  2. PowerBuilder
  3. # Permalink

Hi David,

It may be that the PowerServer conversion into JavaScript cannot handle the pointer nature of Message.LongParm when used with "address" format.

I read through PowerServer's help file. Format = "address" is *NOT* part of the formats described explicitly. See PowerServer 2017 R2 (PB Edition) Help > Supported PB Features for PowerServer Mobile > Functions > System Functions > Supported Functions > Data Type Checking and Conversion for description of supported string formats.

HTH /Michael

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 25 May 2018 14:52 PM UTC
  2. PowerBuilder
  3. # 1

Hi David;

  Yes, that property is supported and I use it all the time in my Web Apps & framework ....

HTH

Regards ... Chris

Comment
  1. David Vasconcelos
  2. Friday, 25 May 2018 16:15 PM UTC
Could there be some setting on the appeon web tool kit that I don't have on when I convert?

  1. Helpful
  1. Chris Pollach @Appeon
  2. Friday, 25 May 2018 18:33 PM UTC
As an example ....  Message.LongParm = 99 in the sender and then use an OpenWithParm ( ) command or Object.Trigger Event xxxx to fire the receiver and have it read the Longparm value.



Note that numbers are passed in DoubleParm not LongParm.



 



 

  1. Helpful
  1. Roland Smith
  2. Saturday, 26 May 2018 01:45 AM UTC
I think you are missing his point. He is using the String function's "address" option to return a string from a pointer.

  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.