Hi Mark;

  That should work as the R2 and R3 run-times are named differently as R3's is now decoupled. So as long as your App and subordinate EXE find their respective run-time DLL's - you should be good to call the R3 EXE from your R2 App and have the chart rendered.

  The other things that you could do is use Roland's Run & Wait code to monitor the R3 App from your R2 App to know when the user closes it before proceeding (if required). You can also use the FindWindow() SDK and Send() PB command to close the R3 App EXE when the R2 App exe is closing if for some reason, the R3 App EXE is still running behind the scenes.

Food for thought.  HTH

Regards ... Chris

I actually just had an 'aha' moment on how to achieve this.   In earlier versions of our application written in PB6.5, PB12.5, PB2019 R2  we have the ability to display embedded web pages.   So all we need to do is use a standalone PB 2019 R3 app to read a datawindow export (PBR) file and then generate the chart html for the web page which can then be displayed in any of our applications.

We were planning on using a text object inside the datawindow to control the graph title, type, columns to be used etc.   so we just need to pass the datawindow into the app and get a file with a web page back!

Mark 

The Apache ECharts is complex JavaScript library that uses the JavaScript execution features we added to the WebBrowser control in PB 2019 R3.

However, it is possible to integrate Google Charts using the WebBrowser control (not inet object).  There is a demo app with Google Charts on GitHub for PB 2019 R2.