Report Generation Toolkit and Application Builder

[Mister_Rose]

I ran this software in the development environment and it works fine. I was hoping that maybe I could step through the code and find the problem, but no such luck. I hate Heisenbugs.

I really am at a loss as to what is happening.

[Wayne.C]

Brian,

This is a long shot.  http://digital.ni.com/public.nsf/allkb/FD7DE8BC8FFC256C862565F4006BE363

Help for Current vi's Path says this.

If you build the VI into an application, this function returns the path to the VI in the application file, and treats the application file as a VI library.

Message Edited by centerbolt on 10-05-2007 03:24 PM

[Mister_Rose]

Good catch and definitely a problem, but not _the_ problem.

I added a widget that handled the current path depending on the system environment used in other spots. Here are the updated VIs.

I added a message box to the template path and it points to a valid file location.

Still no report.

[Wayne.C]

I take it that the vi you posted is part of something larger and that is what is being built into .exe?

[Mister_Rose]

Yes, there is a larger application, but the printing stuff is pretty much self contained.

[Wayne.C]

Suggest you turn printing part into standalone app and see what happens.  Divide and conquer.

[sture]

You could also try wire a true constant  to the "close report" input on "dispose report.vi" that leaves excel open. Also use an indicator on the "dispose report.vi" error output to see if there any errors...

[Mister_Rose · Accepted solution]

OK Ifinally figured out what was happening. It was a less than complete understanding of what to do on my part.

I had added the _Excel Dynamic VIs.vi to my project and was trying to get it to build. What I did not do was to add _Excel Dynamic VIs.vi to the "Dynamic VIs and Support Files" portion of the Build Specification.

I thought that by including the dynamic VIs into the project gave the project manager the information it needed and this was passed off to the application builder. The reason I thought this because I had a previous project using the Office report toolkit that had the same problem. I was able to solve this by adding all the VIs in the toolkit to the build. After that it worked fine, although my project was horribly cluttered.

Anyway, problem solved.