executable won't talk to Excel

[DianeS]

I have an application which I am trying to build into an executable.  I am using LV8.6.  The application communicates with Excel via ActiveX references, methods, and properties.  When I attempt to run the executable and open an Excel file, I get error 7.

I know there is a KnowledgeBase article relating to this exact issue.  However, when I click on the link to the article, I receive a message saying I am not authorized to view it.  What magic level of access do I need in order to be able to take a look at that article??

I have also browsed the Discussion Forums on this topic already, and nothing I do (including the Dynamic Excel VIs in my build, etc.) is working.  Can anyone help??

Related:  I am building an installer for this app as well.  I'm using a batch file to call two other executables, which contain third-party installers.  One of the third-party installers seems to be colliding with the NI installer.  I am getting the error "two installers are trying to run at the same time."  From research on this forum, I thought that the use of the batch file was supposed to solve that problem.  Does anyone have any insight on this?  I have added a "pause" command to my batch file before calling the first installer, but that hasn't helped.

I would really appreciate any insight that anyone has to offer.  It's my first time up the learning curve on these issues and I'm getting frustrated.

Thanks!

[DianeS]

Here is the vi in which I try to open an Excel file, if that's at all helpful.

[OliviaC]

Hi Diane,

The link to the Knowledge Base is broken (thank you for pointing that out) but it's suppose to say is that Error 7 occurs when the Report Generation Toolkit's dynamic VIs are not included during the build process. You don't seem to be using it but here is what the article suggests:

LabVIEW 8.6 uses Report Generation Toolkit 1.1.3 which uses LabVIEW Classes. The Application Builder only lets you add files from your project therefore you have to add this file to your project explorer first. In your Project Explorer window right-click on My Computer and select Add Folder. Then select NIReport.llb in C:/Program Files/National Instruments/LabVIEW 8.6/vi.lib/Utility/. Finally, you can add it as a dynamic VI inside the Application Builder.

If you don't think I'm referencing the right KB please let me know what the title of the KB should be and I'll see if I can find the one you are looking for.

Here are few other links that might help as well:

http://digital.ni.com/public.nsf/allkb/C38CE3F30542D65B86256F0E00740DD8?OpenDocument 

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000kIHWSA2&l=en-US

http://digital.ni.com/public.nsf/allkb/2AE85CF95217E60786257540000D818C?OpenDocument 

[DianeS]

Hi Olivia,

Thanks for the reply.

I managed to track down the error on my own, though -- it was occurring earlier in the execution flow.  There was a call to a file (which I never use) that specified a relative path -- a relic left over from the previous developer.  I finally found it.  Once I found it, fixing it was not a problem.

I also decided to just use my batch file to call all of my installers, instead of running the NI installer and using that to call the batch file (from which I was running my third-party installers).  I get a lot more control that way and can explicitly prevent collisions.

Thanks for your post, though!

Diane

[dbtestcon]

Why doesn't this JUST work?

Why do I need to go hunting around and adding extra libraries to my project?

Why can't I just build an execuable and have it work like it did in the development?

I am getting pissed that NI is bugging me weekly for more $$$ to renew my annual subscription for updates to stuff that never gets fixed!!!!

[DianeS]

If you just want to rant, do you suppose you could start your own thread to do it?  Your comments don't seem to have much to do with the problem or the solution.