Hi, Cathy -

This is purely a guess on my part, but it would appear you might be able to set this via the PB OLEObject object and by navigating through the Excel object model:

    https://learn.microsoft.com/en-us/office/vba/api/overview/excel/object-model

I'm not familiar with this "Program Name" property, so I'm unsure if this is a built-in property (my slightly older version of Excel does not display it) or if it is instead a custom property.

I've also never delved into this area, but it appears that the object model hierarchy may be something like this:

Application -> Workbook -> BuiltinDocumentProperties (a collection) -> DocumentProperty
  or
Application -> Workbook -> CustomDocumentProperties (a collection) -> DocumentProperty

You may wish to experiment and see if you can navigate through the Excel object model using PB OLEObject variables to see if you can first find the Program Name property. Once you can find it, you should be able to subsequently set its value. This will have to be done after the .xlsx file have been created, of course.

Best regards, John

Thanks John for your response! 

I found a work around.  So instead of dw saveas excel, i'm saving it now as csv so syncfusion can open it, then i can manipulate the data in syncfusion (ole using Syncfusion.ExcelWrapper) then from syncfusion save it asexcel.   End user save as excel, they will still get excel file at the end of processing.

Regards,

Cathy

Hi Cathy,

I understand you set this as resolved and I'm glad you found a work-around, but I'm curious as to what version of PB you are using and the specific code you use when executing the SaveAs function. The reason I ask is because as I understand it, the Program name property is an automatically updated property. While John's suggestion was a good idea, this property is not one of the ones that is modifiable via the BuiltinDocumentProperties collection via OLE, as it would be with, for example, the Comments property. The Program name property should be auto populated upon executing dw.SaveAs() and so I'm wondering if this is a bug depending on the version of PB you are using and/ or how it's coded.  Thanks.

Regards,

Mark

hi Mark,

I'm on PB 2022 R2 and thought the same thing that it could be a bug for this version but can't validate since i don't have lower PB versions on my machine.

The syntax is a straight forward dw.SaveAs().

thanks,

Cathy

Please submit a bug report requesting that this property be set.

Submitted Bug 11064.

Hi Cathy,

It would appear from my testing this is a field that only MS Office can populate, though I haven't been able to definitively confirm this anywhere on-line...and which version of PB you're using seems to be irrelevant. Appeon may be able to confirm or refute this generally but also in conjunction with the library they use to create the Excel file via SaveAs() but I wouldn't be surprised if they can't modify it either. It took a bit to catch on to this because usually I either 1) create the Excel file using OLE or 2) most if not all of my SaveAs() calls are then followed by accessing the file via OLE due to the current limitations of the SaveAs() function...so my Excel files always had that property populated.

A workaround, and maybe simpler than what you're currently doing, is once the file is created, open the file via OLE and simply call the Save function and then this field will be populated. No changes are required to be made once you open the file, just the fact that you saved it via OLE is all that's needed.

I was going to update the ticket with these comments but, and correct me if I'm wrong, it appears the ticket you created is private?!

HTH...regards,

Mark