Getting "Save File" permission message related to Report Generation Toolkit

[MoReese]

I started having this problem about a month ago.  It does not affect the operation of my project but is a minor nuisance, but a nuisance none the less.  I opened a couple of Excel Specific VIs.  I did not nor did I attempt to make any changes, I was just curious as to their content (truth is I wanted to see how the active X controls were being used).  Ever since then I get the attached messages when saving my project and have not been able to get rid of it.  When OK is pressed, a Save As dialog box appears (see attached) pointing to the NI directory which contains the Excel VIs for the Report Generation Toolkit.  I press cancel and am able to save my project VIs just fine, but I would like to get to the bottom of this problem.

I would not think that simply opening a VI would cause this behavior.  I should also mention, it not only attempts to save the VIs I opened, but every RGT VI that is a part of my project, which is even stranger.  I have not attempted a reinstall.  I was hoping for something a little less drastic, and that won't prevent this from happening again, unless I can kill my curiousity that is. Is there a setting somewhere which I am missing?  Thanks in advance for your assistance.

Reese

[MAltmann]

Hi MoReese,

This behavior is typical.  If you have opened the VI and looked around it may have updated the active X calls to a newer version of active X.  You can try and remedy the VIs asking you to save them by doing a mass compile of the RGT.  You can find mass compile in LabVIEW by going to Tools >> Advanced >> Mass Compile.  Then you can select the vi.lib folder and then the report gen sub folders to mass compile them.

[MoReese]

Sorry for the delay.  Your suggestion of Mass Compiling the vi.lib sub-folder did not work.  Attached is a screen-shot pointing to the sub-folder that I mass compiled, but the same message still appears.  Does anyone have any other suggestions?  Would performing a mass compile of the entire vi.lib folder be helpful?  Thanks in advance.

[Dan_N]

Hi MoReese,

Try Mass Compiling the entire _office folder. There are some subVIs related to MS Excel that are not located in excel.llb. Post back if that does not work. 

Best,

Dan N

Applications Engineer

National Instruments 

[MoReese]

It did not work.  In fact, it called out four bad VIs (see attached).  But I think this is probably normal behavior.  All the VIs in question are broken due to an unwired input on the bundle.  The bundle is the only thing in these VIs.  Could you please verify that this is the case.  It said the mass compile was complete and I am assuming that it did compile the rest of the VIs, correct?  Unfortunately I am still getting the same message.  Do you have any other ideas?  Anyone?  Thanks again for your assistance.

[Dan_N]

Hi MoReese,

You are correct; those VIs are supposed to look that way. One clarifier: when the dialog box pops up in your project to ask you to save the Excel VIs, have you ever clicked Yes? Try first logging into your machine as an administrator, which will give you permission to update the report gen VIs (this is likely the cause of the error poup that you are seeing), and then save all of the VIs when prompted. Mass compiling the VIs is equivalent to saving them. If you haven't clicked Save in your project, go ahead and do so the next time that the dialog pops up. Also, when looking at your screenshot, the reason that the project asks you to save all of your report gen toolkit VIs is because you're opening up Excel Import Module.vi, which has many dependencies.

Best,

Dan N

Applications Engineer

National Instruments 

[MoReese]

Nope, it still didn't work.  I have full priviledges on my computer.  When I select yes to save, it comes up with the same dialog saying I don't have permission to save it.  Is it possible to reinstall just the RGT, rather than the whole of LV?  Any other suggestions would be appreciated.  Thanks.

[Alisha_P]

You should be able to install just the report generation toolkit, without installing LabVIEW (this could possibly depend on how you are installing it). I don't know if that would fix things for you, but you could definitely try it. Have you tried repairing the toolkit (and maybe LabVIEW too) through Control Panel>>Programs and Features>>National Instruments Software. It does seem strange that you're getting all of these permission errors when you're the administrator.