Using external llb when building applications

I would like to be able to update the SubVI's that an executable uses, but am having problems editing them after installation of the build application.
I am using the option "Small target file with external file for SubVI's" in the application builder, but I don't seem to be able to open the VI's present in the external library ("data.llb") after installation. I get the error message "ressoruce not found", when trying to open the file in LabVIEW. Does anyone know what might be the problem.

Caveman wrote:
> I would like to be able to update the SubVI's that an executable uses,
> but am having problems editing them after installation of the build
> application.
>
> I am using the option "Small target file with external file for
> SubVI's" in the application builder, but I don't seem to be able to
> open the VI's present in the external library ("data.llb") after
> installation. I get the error message "ressoruce not found", when
> trying to open the file in LabVIEW. Does anyone know what might be the
> problem.
Those VIs get just as much stripped of their front panel and diagram
unless you specifiy not to do that in the VI settings in Application
Builder. Without front panel you can not load a VI in the LabVIEW
editor. It is only good for calling
by reference.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Similar Messages

Error when building application with Excel included

Hi All !
I've read several post on problems with Report Generation Toolkit when building applications that uses Excel or Word interactivity.
I've included both _Excel Dynamic VIs.vi and _Word Dynamic VIs.vi in my project and added them to the dynamic vis and support files.
When building I get the error :
The VI is broken. Open the VI in LabVIEW and fix the errors.
C:\Programmer\National Instruments\LabVIEW 8.2\vi.lib\addons\_office\_exclsub.llb\_Excel Dynamic VIs.vi
When opening that VI there is no broken arrow and all the vi's included in this is not broken either.
I've tried mass compiling and so on but so far luck.
Regards Morten Kahr
Regards Kahr
Certified LabVIEW Architect
CIM A/S

If you do a search on this forum you will find this to be a common and vexing problem. I myself had this same exact problem about a year ago, and it took me the better part of a day to track it down. As you will find by reading the various threads on this problem, there seems to be no specific cause for this, and it remains a mystery, and the solutions are no better than chanting voodoo, and probably just as effective.
One thing you can try is to force a recompile of your VI hierarchy. Open you top-level VI. If it's set up to run when opened, stop it. Hold down the Control key and click the run button. This will force a recompile of the application. Sometimes this works, sometimes it doesn't. Like I said, voodoo.
Another thing to look for is to check if you are using any diagram disable structures or case structures with a constant wired, as in trying to use the case structure to comment out code.
Are you using classes and passing by reference? There was a mention of this here.

Unresolved external symbols when building release version of DLL

I have C code which I use to build a DLL project. I have used the same code to create this DLL project in several different solutions.
I am trying to build it in a new solution, and can build the debug version, but I receive a bunch of unresolved external errors when I try to build the release version.
I have painstakingly compared the project release properties with the debug properties, and with the release properties of the same project when I have included it in other solutions. I can't find the problem.
Here are a few of the errors:
1>OLDNAMES.lib(access.obj) : error LNK2001: unresolved external symbol _access
1>Cbase_filedir.obj : error LNK2001: unresolved external symbol __imp__strchr
1>Cusage.lib(CusageWebLog.obj) : error LNK2001: unresolved external symbol __imp__strchr
1>Cbase_filedir.obj : error LNK2001: unresolved external symbol __imp__fopen
Any Suggestions?
Mike

Hi Mike,
Thanks for posting in MSDN forum.
1.Please check project properties->Linker->Additional dependencies has the same libs in both debug and release version. Maybe the lib you added in bebug version but not working in release version.
2.Double check there is no code in something like that #ifdebug ... #endif
3.please use the same character set in your dll or the referenced lib. Both are unicode character set or multi-Bity.
4.Please use the same Runtime library in your dll or the referenced lib. Both are C\C++->code generation->runtime library ->/MD or /MT
Above are some general scenarios, hope this helps some.
Best regards,
Shu Hu
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

How to include external files when building installer for a standalone executable?

Hi,
I was trying to build a stand alone executable from my Labview project and I was able to do it successfully. Now I would like to include a few external .txt files in the installer. Those .txt files have parameters/constants that will be used by the program, and my program needs to load/read them when running. For now I have to manually copy/paste them into the target machine, but I really hope the installer can do it automatically. I see there is a "data" folder in the installer, and that's where I hope those .txt files can be added into.
How can I do it? Can anyone give me some suggestions? Thanks!
Rgds
Harry
Solved!
Go to Solution.

Norbert,
I could not find "Add file" when right clicking the project. See attached image please. Under "Project" I do have a "Add to project" but there is no option for external files. I did not find "Source" location either.
What did i do wrong? Is there any version requirement here? I have a 2010 base version. Thanks for your help.
Rgds,
Harry

Labview crashing when building application (exe)

Hi,
I am trying to build an application from a simple labview (2011) vi. All the vi does is sets (boolean = TRUE) a line on the digital output card (NI 9472) when I start running the vi. The program works fine after I have coded it. But when I try to build an exe file (application) of that project, then labview crashes in the build process. Is this a known issue? please help. I am attaching my vi alongwith this email
Thanks
Solved!
Go to Solution.
Attachments:
relayProject.lvproj ‏34 KB
relay.vi ‏21 KB

I'm sorry to hear that gascars. I have downloaded your project and VI and have succesfully built an executable in both LabVIEW 2011 and LabVIEW 2012. Can you please send me a screenshot of the error you are receiving? Also, can you make a simple VI that just adds two numbers and see if that can be made into an .exe.
Thanks
Chris
Chris
National Instruments
Applications Engineer

Why do I get Error 1 when building applications

Estoy tratando de crear un ejecutable en labview 6.1. Pero me sale el siguiente error: Error1 ocurred at GSim Sintax Check.vi:\. Este ejecutable lo estoy generando en una computadora donde no tengo instalado el toolkit de control y simulación sino que copie los vi de este toolkit para usarlos en la aplicación. Que puedo hace para resolver el problema.
Gracias

Hola,
Tomando en cuenta lo que mencionas acerca de que copiaste de manera manual los VIs del Toolkit de Simulación y Control lo que está pasando es que estas funciones no están debidamente actualizadas en LabVIEW; tu aplicación debe tener dependencias a subVIs que no se pueden encontrar.
Mi recomendación entonces es realizar una compilación en masa (mass compile) de los directorios o librerías que contienen los VIs del Toolkit; posteriormente intentar de nuevo construir el ejecutable. Para realizar dicha tarea debes en LabVIEW debes ir a:
Tools » Advanced » Mass Compile
Puedes encontrar mas información sobre lo que hace la compilación en masa en el siguiente enlace:
http://digital.ni.com/public.nsf/websearch/654877E62A97B72986256C95006F9B24?OpenDocument
En caso de que el problema persista te invito a ponerte en contacto con Ingeniería de Aplicaciones de National Instruments; conoce nuestras opciones de soporte técnico en español:
http://www.ni.com/latam/soporte
Saludos,
Fernando Domínguez
Applications Engineer
National Instruments
Fernando D.
National Instruments

Using external libraries in eSWT on 7.1

Hi again.
Is it still possible to use external libraries when developing applications for Handhelds on Mobile 7.1 (eSWT)? Or do we have any restrictions here?
Thanks,
Sascha

Hi,
as long as your have POJOs it should be ok to use them still.
Regards,
Oliver

Lost Page on when you should use MVC vs when you should use web forms

I read a page last week. I think it was on MSDN. It was talking about the relative merits of MVC and web forms. However, unlike the page http://msdn.microsoft.com/en-us/library/dd381412.aspx,
which merely states the advantages and disadvantages of each format, this page went on to state something like:
You should use MVC:
when building web apps that do this
when you web app needs that
when you are doing the other
You should use web forms:
when building these other kinds of web app
when your web app does this other thing
when your web app does this.
Does anyone know the page to which I am referring?
(Oh and since when did it become impossible to paste anything into a question or reply block in MSDN forums. This makes it very difficult to paste in page links.)
Also I am not seeing an appropiate forum in my forums dropdown list. So if a moderator wants to move it to the right forum I would appreciate it.
Edward R. Joell MCSD MCDBA

@Darnie Graceline Selvamary Thangalazar
The first link is not what I was looking for as it tells the difference between MVC and Web Forms but not which is better for what.
The second link does get more into which is better in certain situations but doesn't really analyze each type of project and specify that this is good for web forms and this is good for MVC. However, it does provide some ways to analyze if your
"situation" would be best served by using web forms and which would be best served by using MVC.
It specified that if reaction time is an issue then MVC is the answer. This is good because with our excruciatingly slow network we need apps that take inherantly as little time as possible to load.
I took another look at the link provided by gaurav. Turns out that link has a link to an article by Dino Espisito which actually has the statement that I referred to above i.e. if your app has a lot of busines data. After two years, that
is as much as I remember of that page. So in fact indirectly gaurav found the page I was looking for.
Too bad I did not re-read this link when I started the current project, though. One thing each of them says is that if your team (in this case me) has not had much experience in handling html elements directly then MVC is not a good fix for them.
For the last 6 months theis has been a major learning process in using JQuery, AJAX, and MVC to accomplish tasks which I've could have done using server controls and web forms with my eyes closed. Too bad they don't make MVC so that you can use server
controls with it.
However since this thread is so old and unlike "Whose Line is it Anyway?" the points
do matter. I am going to award the answer to gaurav. Thanks everyone for providing some very interesting links on MVC.
Edward R. Joell MCSD MCDBA

Error 1003 occurred at Open VI Reference in Dist Copy Non-VI Files.vi- Dist Build LLB Image.vi- Dist Build App Image.vi- Build Application.vi

When trying to build an application using labview 7.1 and windows XP, I get the error
Error 1003 occurred at Open VI Reference in Dist Copy Non-VI Files.vi->Dist Build LLB Image.vi->Dist Build App Image.vi->Build Application.vi
I've tried the crtl-shift-run as well as a mass compile and I still get the error.
Any ideas?
Thanks,
Mike

Hopefully this thread, or this KB article might help.
It seems like this could come from a lot of things, but there's suggestions in those which might lead you in the right direction
Message Edited by Day on 09-22-2006 02:07 PM

Porblems with built application, using wordsub.llb

I am trying to compile a Vi that uses the New Report.vi to create a test datasheet. When I run the Vi in development mode, it works ok. When I run it after using the "build application" fucntion, the vi gives an error (Code 7). The description for the error says something about the "open vi reference". I believe the error has something to do with the "word" related vi's that are contained in the wordsub.llb.
Does anyone know what I am doing wrong?
Is it something with the build process?

Are you using LabVIEW 8.0 or later? If so, the instructions for building an executable are incorrect...they state that you must add _wordsub.llb as a Support File, but you should actually add _wordsub.llb\Word Dynamic VIs.vi as a Dynamic VI when building the executable. Also, if you are calling any Excel-specific VIs, you would need to add _excelsub.llb\Excel Dynamic VIs.vi as a Dynamic VI as well.
Try this out and see if it works...we are planning on changing the documentation for the toolkit for the next release to indicate the different steps you need to take for building an executable with Report Generation Toolkit VIs in LabVIEW 8.0 versus previous versions.
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Error 1 when building my application in Labview 2010 Version 10.0f2

I am getting the following error trying to build my application in Labview 2010 Version 10.0f2 and I get the following error:
Error 1 occurred at Invoke Node in AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
Method Name: Linker:Write Info To File
I have searched and can find no real sollutions to this problem. I did the updates and still nothing. Now I can't even build an app with Laview 8.6. I reference several .NET items and refuse to rebuild each and every one of them. My only option at this point is to uninstall all Labview and then reinstall 8.6 so I can do something.
Help if you can.

Hello RBrown
I am really sorry for this inconvenience! This is a known issue.
Can you please attempt the following for me:
When you are building an application, under Advanced please check the last box "Use LabVIEW 8.x file layout"
If that doesn't work, you may need to rebuild the LLB in a separate directory with new names, and use it as the build inclusion.
Here are some forum posts strictly for your information:
I have found users that have had similar issues. I am trying to make this workaround work for you.
http://forums.ni.com/t5/LabVIEW/error-1052/m-p/912192
This is a known issue that some customers have already commented on:
http://forums.ni.com/t5/LabVIEW/NI-Please-don-t-put-illegal-vi-names-in-your-toolkits-thanks/m-p/745...
I have filed a corrective action for this issue and I will add you to the list of individuals who need this issue resolved.
Sincerely,
Greg S.

I get a "vi is not executable" error when building an application.

I have an ongoing project that has worked fine in the past when building an application. I have recently added some report generation toolkit vis(Excel) and get an error for some of the ni vis and some of my own that call lower level excel vis. The error is that he vi is not executable, however they run fine in the development environment. I do not get this error if I save all vi's into one llb with save with options command and then build. However, when I try to run the app, this error re-appears. Also, do I have to add the dynamically loaded vi's that are part of the toolkit in my build script? Could this be the cause of the problem? If so, what's the best way to find all of them? Any suggestions?

You have hit in on the nail! You do need to add the dynamically loaded VIs when you are creating an executable from your VI. You need to add _wordsub.lib and _exclsub.lib as dynamically loaded VIs into your executable. Try this and let us know if you have any more problems with it.
J.R. Allen

Empty report returned from WEBI and Crystal report when using external hier

Hi,
WEBI and Crystal report build from BEX query returned empty report when we used external hierarchy 0PROFIT_CTR. In BEX we don't have any problems with it.
No authority check is perfomed on the hierarchy when we start the report in WEBI/Crystal. Only check on the hierarchy is performed when the root authorization is assigned to the user

We using BO4 SP12

Using papervision in flash builder and getting TypeError: Error #1009: when using object.pitch(5)

When i use papervision in flash builder and i am doing a test, when i render a sphere using papervision with the following code it renders me the sphere.
When i add a line sphere.pitch(2); ||
sphere.yaw(2);
sphere.roll(2);
i get the following error,
TypeError: Error #1009: Cannot access a property or method of a null object reference.
at PvTest/onRenderTick()[D:\Android 3D\PvTest\src\PvTest.as:39]
Can anyone help me figure out the error
For additional Info, these are the imports i am doing:
import org.papervision3d.objects.primitives.Sphere;
import org.papervision3d.view.BasicView;

I followed the steps and read some of your comments on the same top topic in another thread. When I put it on the first frame it was okay but the next button on that page had the same problem. So what I am guessing is that I have to either create a document class or put the actions where the buttons are. Am I understanding that correctly? In the other thread in which you helped someone else; there was so comments about document class. I found a tutorial on it and the way I understand it is that it you can put you actions in an external document. But you have to include in the event listener the frame in which you want that action to happen.
Thaks for your help. And patience.

When using external-scheme what is still stored on-heap?

Hi all,
If I have a scheme like this...
<distributed-scheme>
    <scheme-name>distributed-scheme</scheme-name>
    <service-name>TestDistributedService</service-name>
    <backing-map-scheme>
      <external-scheme>
        <lh-file-manager>
          <directory>/temp/odc-data</directory>
        </lh-file-manager>
      </external-scheme>
    </backing-map-scheme>
</distributed-scheme>...when I put data into a cache what is still stored on the heap?
When I do a test I can see that obviously the data is not on the heap as I can add massively more entries before I run out of memory.
Using the VisualVM tool's memory sampler I can see a similar number of instances of com.tangosol.util.Binary as I have entries - so are they keys still on the heap?
If I add indexes then I can see that these are on the heap, so I will have keys and indexed values on the heap. I end up with twice as many instances of Binary as I have put entries, which makes sense as the index contains a references to the Binary keys.
The reason I ask is because I configured a "Dev" version of our application that uses <external-scheme> everywhere you would normaly use a <local-scheme> so we can run a version of our application for Dev testing on development machines with limited RAM. It needed a few tweaks and a custom DefaultConfigurableCacheFactory but seems to work fine. I am now trying to figure out just how much space we save and how much "data" is still on the heap.
Cheers,
JK

Thanks David.
So with an external scheme we will be able to save the amount of space taken by the cache values. Now if I could just shift the indexes (which take quite a bit of space) that would be a bonus. I know it sort of defeats the point of having an index but I am trying to run the app on a small Dev server so I am more interested that it works functionally than how fast it is. If the app was 3.6 I might be able to do something clever with custom indexes - then again we could just remove the indexes.
Cheers,
JK

Using external llb when building applications

Similar Messages

Maybe you are looking for