1. Josh Turner
  2. PowerBuilder
  3. Friday, 26 October 2018 19:29 PM UTC

3 of our clients are reporting strange formatting characters displaying in their rich text control. The string of characters is always the same and it's always at the beginning. They can delete the characters but show up again later. The characters are:

ogrowautofitfeaturethrottle1

They are on PB 2017 R3. Has anyone else seen anything similar? We can't seem to repeat it in our dev environments and I'm not even sure it's consistently doing it for the clients.

Attachments (1)
Josh Turner Accepted Answer Pending Moderation
  1. Friday, 30 November 2018 17:50 PM UTC
  2. PowerBuilder
  3. # 1

Looks like the bug from the past:

https://archive.sap.com/discussions/thread/3795913

Comment
There are no comments made yet.
Josh Turner Accepted Answer Pending Moderation
  1. Friday, 30 November 2018 17:43 PM UTC
  2. PowerBuilder
  3. # 2

I've discovered more. Comparing a corrupt note vs a good note, it looks like anywhere there's a '\n' in the blob string, it's being translated as a newline character and converting to 'x0a'. So 'footery720\\nogrowautofit\\' becomes 'footery720\x0aogrowautofit\\' and 'formshade\\nofeaturethrottle1\\' becomes 'formshade\x0aofeaturethrottle1'. The end result is that the rich text editor can't interpret the x0a and it shows up on the note itself. Now to figure out if it's the database, PB, or something else.

ASA 12
PowerBuilder 2017 R2

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 26 October 2018 19:50 PM UTC
  2. PowerBuilder
  3. # 3

Hi Josh;

   Yes ... very, very strange!

Per chance, you it be that the 3 PC's that are having the RTE issue also have a mismatched PB run-time?

Regards ... Chris

Comment
  1. Josh Turner
  2. Friday, 26 October 2018 19:54 PM UTC
possibly. I'll double check that. Thanks
  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.