There might be an easier way than working with an Active-X control. You can dynamically create a DWO in a PBL, add that PBL to the library path, and when you run the report, it'll find that copy of it.

Here are the basic steps we've used when overcoming similar issues (nested reports where we need to modify the retrieve or some other object, but can't get to it through other means):

First, save original datawindow you want to modify with different name, delete original (make sure it's in your PBR, or it won't be available at runtime)

At runtime:
- check to see if runtime work PBL exists (preferably in the user appdata directory, or similar "local" place), create it if it doesn't
- check to see if dwo in the pbl exists, delete it if it does (do this 2 times in a row, as the delete step sometimes fails to delete the object and doesn't report an error)
- create temporary datastore, load it with your newly named "original" DWO
- make changes to controls as needed
- use describe to get syntax (ds.describe("datawindow.syntax"))
- use LibraryImport to take the syntax and save it into the PBL with the object name used by the report
- run report and you should have your newly colored graph lines

It sounds like a lot of steps, but it lets you do all of your work in PB without involving other languages & objects.

Thanks to all the suggestions and replies.

The graph has to be on the datawindow as its a 'Work Order' showing trending data points on the work order asset.

I've already tested using the MS graph control and it still shows up and prints fine.

just have to figure how to populate it from the database now. LOL

thanks agaiin

Mike

Hi Michael;

  Another approach that I have used when the graph is part of a standard report is if the App users would be OK with the report being in PDF format.

  If PDF is OK - then you can produce each part of the report as its own PDF file. Since the graph is now running 1:1 with its DC/DS, you can now do the colourization as required. Once the report PDF pieces are produced, I just merge the PDF files into one for the illusion of a Composite report.

  For the PDF merging, I use the free PDF ToolKit: https://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/

FYI: I have a demo App for the PDF file merging as an example.

HTH

Regards ... Chris

Thanks Chris.

Guess I'll do a ole object using microsoft graph control.

Mike

Hi Mike;

  That only works if the parent (or main DWO) is a graph. It does not fire for child DWO's.

Regards ... Chris

Thanks all for there replies. :-)

Miguel

Added a ue event for pbm_dwngraphcreate but its not begin called.

could it be because it is a composite graph and is a child object of the main datawindow?

thanks

Mike

Yes previously it was also possible:

I've digged up some "old" code where in the pbm_dwnGraphCreate()  (add it manually if it's not present yet in the events list of the dw control):

// Just replace "gnv_app.il_CM_CREDICA_BLUE" with a call to the RGB() function to set your own colour

long ll_count, ll_data_count, ll_ret

ll_data_count = this.datacount("gr_effort","")
this.SetSeriesStyle ("gr_effort", "", linecolor!, gnv_app.il_CM_CREDICA_BLUE )
for ll_count = 1 to ll_data_count
  this.SetDataStyle ( "gr_effort", 1, ll_count, foreground!, gnv_app.il_CM_CREDICA_BLUE )
next

Hi, Michael -

The errors you're getting is because you are trying to use methods (DataCount, CategoryCount, etc.) of a DataWindow Control as properties of a child DataWindow via dot notation.

PowerBuilder 2019 allows you to do this using the new UI themes feature: https://community.appeon.com/index.php/blogs/recent-blogs/codeless-enhancement-of-your-app-s-ui-ux

I'm not aware that you can do this programmatically, but maybe somebody else here knows something I don't.