building application with wordsub

[JimN]

I am building an application that uses some of the report generation toolkit. If I build it, it comes up with errors relating the the wordsub.vi.

I followed the guidance, which says to add in the Word Dynamic VIs.vi (as well as the Excel Dynamic VIs.vi). I add them in using the "add dynamic vi" button under source files. But during the build, I get the following error: Error 1003 occurred at C:\Documents and Settings\James Nauman\My Documents\LabVIEW Data\<"My application name">\internal.llb\_Word Dynamic VIs.vi

My application is under a file in c: and the Word (Excel) Dynamic VIs.vi are in the original addon/wordsub dir.

Jim

[JimN]

Just an update. I copied the wordsub.llb to my application directory with the same result.

Jim

[Scott Y]

Hello JimN,

There is a knowledgebase describing this error and a solution, available here. As you are using dynamic VIs in your application, I would suggest opening up each of the dynamic VIs and following the suggestions in the knowledgebase.

Scott Y
NI

[JimN]

Thanks, the Word Dynamic VI's.vi did have a broken arrow. I had to replace the write jpg vi, then everything worked.

Is there a good reference for file structuring. It seems half my problems are related to vi's linking,relinking to somewhere else than where intended. I am trying to build several variations of one application with minor changes. I open vi (A) up and everything works. But, then I open up vi (B) and everything is linking to (A). I cure everything and close (B), but then when I go back and open (A) everything is linking back to (B). So on and so forth.

I have up to 5 variations on an application, and pretty soon everything is linking all over the place.

I need some basic references (with examples) of how to structure my librarys, directorys, applications, subvis, and what the differences all mean. The getting started with labView is too general. Are there any knowledge base areas discussing this and common errors?

Thanks for the help.
Jim

[JimN]

I went on to the next app build and came up with the same error regarding 1003 for the internal.llb error on the Word Dynamic VI's. This time there were no broken arrows. I force compiled, mass compiled, opened every single vi and saved. Nothing worked. I went from a good build right into the same problem with no noticable errors.

One question I have is that when I add in the Dynamic Word VI's as a dynamic vi in the app builder I see double copies of some vis in the source files. Some originate with the toplevel and some originate with the dynamic Word VI's. Would this cause the problem, if so, how would you get rid of the duplicate?

Jim

[Scott Y]

Hi JimN,

I am not clear exactly what you mean by seeing duplicate source files. Would it be possible for you to post some exact steps to reproduce this behavior? If you can also include some screen shots of the duplicate files it would be very helpful.

Scott Y
NI

[JimN]

My mistake, the duplicates are under vi settings. For instance, I have 2 font.ctl, 2 Find First Error and Warning.vi, and a couple of triplets.

Under the source files are just my app and the Word Dynamic VI's.

Sorry but I have no way to take a screen shot.

Jim

[Scott Y]

JimN,

I am not sure why you see the duplicates under that section either. Are you about to remove the duplicates, and if so that does eliminate the errors you were seeing?

If you are running on a Windows operating system, you should be able to take a screen shot with with printscreen key. This will place a copy of the screen in the clipboard. After that you can use mspaint to crop the image and save it to a file. From your earlier post, it looks like you are running on some type of Windows OS. Is there another reason why you cannot take a screen shot?

Scott Y
NI

[JimN]

Screen shot attached:

[Scott Y]

Hi JimN,

I suspect the duplicates you are seeing have been caused by the way you added the dynamic VIs contained in _wordsub.llb

Inside the _wordsub.llb there is a VI named "_Word Dynamic VIs.vi". This is a special VI which was never intended to be run. The purpose of this VI is to to allow you to easily include all dynamic VIs by only including this one VIs.

I just built the "Line Graph (Word).vi" shipping example into an executable. The only special step required to have it run without error was including the "_Word Dynamic VIs.vi" as a dynamic VIs. I would suggest starting over with a new build script for your application and including only this special VI.

Scott Y
NI