Programmatically Relink Invoke Node while in Executable

[eyang]

Hello,

I am using Report Generation Toolkit generating Excel files. I run Office365 on my PC but some computers have slightly different Excel builds and this causes errors(Not allowed to change Excel builds). In my specific case, the "ExportAsFixedFormat" property requires me to "Relink Invoke Node" per computer and rebuild the exe.

Is there a way to "Relink Invoke Node" can be done while in an executable. I found that there's a new fancy feature in LV18 "Type Specialization Structure" but doesn't seem to work in an exe. It does speed up my process but not perfect, still have to re-compile on the machine.

Has anyone found a solution to trying to do this? I may be doing it completely wrong.

Thanks in advance,

[mcduff]

The below is in .NET, I am sure the properties also exist for ActiveX.

Can you query your version/build and then decide what node to use? I have no idea if this will work.

mcduff

[eyang]

Hi Mcduff, 

So one issue with this is I cant use a regular case statement because one of the invoke node calls is broken on my PC but not the other PCs.

Thinking about this more, what I am trying to do might not be possible because it probably requires every version of Excel installed on my PC. Might just have to create multiple VMs and be stuck with what I have.

Thanks,

[GerdW]

Hi eyang,

one issue with this is I cant use a regular case statement because one of the invoke node calls is broken on my PC but not the other PCs.

You can overcome this by:

- create code for each version of Excel

- create a check, which version of Excel is available

- load the VI suitable for the installed Excel version using VIServer functions and run it…

[mcduff]

Can you make the subVI that calls the invoke node dynamically using VI server. You can call a VI from an exe. Have a VI for each Excel version.

mcduff

EDIT: GerdW beat me to the post.