Rich text issues are resolved with the latest R3 Build 1880 which uses the old TX text control.

RICH TEXT does not work.  It does not render / print properly.  It does not work properly.

It does NOT WORK IN R2.

It does NOT WORK in R3.

More than a year has gone by and we have spent tens of thousands on powerbuilder subscriptions/licenses and appeon has failed to deliver a single usable upgrade to the product.  We had a more reliable product when SAP managed powerbuilder.  Sure, they were literally doing NOTHING to the product.  But at least they didn't BREAK mission critical features while pretending to 'upgrade' them.

Hi Josh;

  The return of the TX control was and IS scheduled for PB2018.

FYI:  https://www.appeon.com/developers/roadmap  (RichText Backwards Compatibility)

Regards ... Chris

I guess R3 was just released a couple days ago and still no movement or even ACKNOWLEDGEMENT of this bug with the rich text datawindow edit control. Using the old TX Text Control is STILL documented as an accepted solution or workaround (it isn't). This bug was reported in January 2018 and is a critical error for our applications. Our customers are unhappy and so are we. While I'm a huge supporter of PowerBuilder and its community, my faith in Appeon's ability to keep PowerBuilder alive and well is dwindling. The bug reporting system is apparently a joke. Not only do you have to spend a large amount of time and energy writing specific code samples to PROVE a bug exists, but when you finally do it's in a perpetual state of "Scheduling" without actually ever being scheduled or even publicly documented as a known bug. Sorry to be such a downer.

We have a licensed PB 12.6 in which the old control is working.

Can't we somehow use that control (already paid for) in pb2017?

I don't really know why Govindo Lopez says on "https://www.appeon.com/standardsupport/search/view?id=894" that the priority has been lowered to P3.

Quote: 
"We have lowered the priority of your issue to the default P3 to be consistent with the priority level definitions in our support policy posted to our Website: https://www.appeon.com/sites/default/files/pictures/Downloads/Appeon_2017_Standard_Support_Plan_Description.pdf"

So I've read the pdf he refers to and it says: 

"(c)  Priority Three (“P3”):  The Supported Programs are useable, but its functionality is seriously 
affected such that development/production can continue for a reasonable amount of time before the 
problem becomes critical.  A workaround exists that is commercially reasonable to implement. "

I don't think the workaround of buying the old control is a working solution, as some people have clearly stated that it's not working as before and neither is it "commercially reasonable".

We've come to the point of having only 65 days left of our yearly subscription and we've not been able to do anything else then test PB2017, we've not been able to bring our production to any production environment, since we depend on the RTE control. Management at the company I work for is disappointed with this.

In other words, I think this should be a P1 by now.

Kind regards,

MiguelL

Has there been an update to the Rich Text issues in PB 17 R2?  We are running into similar issues.

Thanks,

Jeff

Hi Josh;

     I have raised your concerns up to senior management.

Regards ... Chris

Hi Josh,

I am having the same issue. Was told the fix would be in R2, downloaded R2 today but no it works the same way.... no fixes. I have patiently waited for a month on this. This is crazy, I don't know Appeon team management is thinking. What is the use of all the enhancements when you cant make simple thing such as RTF to work!!

Ravi