Stand-alone application to save Excel file developed in PC with Office 2016 running in PC with Office 365

[ICO_82]

Hi ooth,

Great, many many thanks, you hit the nail on the head!
I accepted it as solution because it is exactly the issue and after I learn how to develop a Packaged Project Library maybe I will be able to fix it.

[DavidBoyd]

I've encountered this issue in the past with the ActiveX "flavor" (standalone 2016 vs O365) causing the problem due to the extra "WorkIdentity" parameter.

You may be able to use a type specialization structure to encapsulate the two variations of the node and let LabVIEW choose (remember, this is a compile time choice, not a runtime choice!) at the time of application build.  It still means that your application must be built with the Office platform in place that you intend to target, so it doesn't help you make a single build for all systems.  It only fixes the "code loads broken" when loading in the development environment if the version of Office changes.

Dave