I'm trying to deploy a Project I developed to run on a colleague's new Windows 11 Laptop. Until now, I've mostly been working with LabVIEW 2019 and 2021, and this Project's code seems to run just fine on both older versions of LabVIEW (I've been running 32-bit LabVIEW, but for this particular Project, I decided to "go for broke" and installed the 64-bit version of LabVIEW 2024 Q3).
The code is fairly straight-forward -- it moves a sensing probe slowly up a subject's arm at around 1 mm/s. Works just fine. I take a little bit of data (start time, start position, desired velocity, end time, and end position), saving these data in a Delimited Spreadsheet. At the end of the trials, I transfer the text data to an Excel Workbook which is a more convenient format for the User to use.
But --- it won't build. Guess who is the culprit (for a hint, look at the Message Title). I got an Error Message that mentioned "Excel Find and Replace (num).vi" (and a few other mentions). Should be simple -- open the VI (LabVIEW kindly provides the address, Program Files\LVAddons\rgt\1\vi.lib\addons\_office\excel.llb\Excel Find and Replace (num).vi. Sure enough, it needs a Relink, which works fine. But I cannot save the result -- it is marked "Read Only", and despite running as an Admin, it persists in denying me the ability to "save the fix". I even tried logging in with my Admin account -- made no difference. I also tried going "up the chain" and trying to turn off "Read Only" on, say, excel.llb -- didn't help.
Doing a Mass Compile also didn't change anything (but it did give me a nice printout of the three Excel routines that failed, mentioning them twice, just to rub my nose in it).
Curiousity (why is Google flagging that as a mis-spelling?) made me look at my LabVIEW 2021 (32-bit) installation for the Office addons. Well, they are right there in vi.lib, not in LVAddons, and they are not protected, so we can patch them.
Is this a "bug", or a "feature"? Is there a way to temporarily remove the Protection on stuff in LVAddons, particularly for the Report Generation Toolkit? We almost always need a one-time patch to get LabVIEW "in synch" with Office. If it matters, under "About Excel" it says "Build 17328-20670", and "Microsoft 365 Apps for enterprise". But it seems to me the problem is in the LVAddons ...
Bob Schor
