11-22-2024 05:05 AM
I need to password protect Excel reports.
In the recent past I found a way to do it but it requires to handle the Excel files already saved and disposed.. I cannot use such solution (that uses OpenXML) in the currect workflow.
I tried to use an ActiveX oriented approach following some of the info collected on this forum.
Unluckly any attempt has failed either because I cannot undestand wich node was being used or because some references were missing in the example provided... the only example I've been able to replicate is this simple diagram:
But as you can see no methods populate the Invoke node ... I cannot understand how to make it work... and this's pretty strange since by any other means report toolkit or any other Invoke Node instances are working fine.
Solved! Go to Solution.
11-22-2024 05:48 AM
This will probably help
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019KZNSA2&l=en-US
11-22-2024 05:59 AM
😓I cannot change neither Labview bitness neither Office bitness... I'm **bleep**ed...
11-22-2024 06:11 AM
Did you try these steps?
11-22-2024 07:37 AM
Excuse me ... I've been foulded/discouraged by the original post that pointed on the bitness.
Anyway I followed your hint and I found to point to the correct object after that I think everything self fixed because now I can see all methods without further need to select the class... weird but it works.
thnx.
11-22-2024 09:07 AM
I think that this fix triggered some issues... now If I try to use something that uses the Report Toolkit I got this:
How can I fix this?
11-22-2024 09:13 AM - edited 11-22-2024 09:16 AM
Maybe click on one of those errors and show a picture of what isn't wired correctly. Then I can compare it to my VIs. For example here is my Find and Replace (str).vi
11-22-2024 09:31 AM
here it is...
the object with unwired or bad terminals should be the Range Invoke node but it looks correct:
11-22-2024 09:33 AM
Wait... I made a Clean Up Diagram and it fixed ...
11-22-2024 10:20 AM
Look at your registry settings too.