Report Writer BEFORE WIndows 10 was SUPER ROBUST! Now that Windows 10 came along there exist many "turds" left in the Registry when folks UPGRADE from Office 7 to Office 10.
What happens is the Registry NEVER NEEDED to be kept clean of extra junk because NOBODY EVER UPDATED Office.
Now every Joe on the planet updates their Windows 10 with the latest Office 10..
What happens if they do NOT FIRST UNINSTALL, is the Registry is left with "turds"
When Report Writer uses ActiveX to make calls to use Word, in the old days, there was a SINGLE key in the registry to allow the calling program to gracefully start Word or Excel, or whatever.
NOW< with Windows 10 there are FREQUENTLY multiple "keys" in a Registry that causxe the LabVIEW Report Writer to "Gag" and "Hang up" doing nothing.
The SOLUTION is for the Report Writer to PARSE the Registry for valid keys and allow the request to be passed to the propper called process.
If this is not clear, please look up the SR below. There are a TON of examples and videos explaining how to fix it.
I have been working with LV since Dr. G was roaming the halls on LV 3...
This is the FIRST TIME Report Writer has gotten "sick".
This is an EASY FIX for the devs and since Report Writer is a purchased plugin they sould be able to update it so it works well.
Currently, they have us fiddling with the Registry or telling customers to uninstall and reinstall Office. That is a BIG FAT NO-NO to big companies because Office WORKS COMPLETELY for them and even programs like SolidWorks and DXP that use Word and Excel for stuff.
My number 831-455-0418
DEVS:
Please see: Request #: 00994109] Can not get EXE BUilder to run on WIn 10
