Applicatio​n Builder Performanc​e?

Hello all.
Can anyone tell me if putting your application through the Application
Builder has a real improvment on performance. Or does it just cut the
size of the exe. down?
Regards,
Steve Drake

> Can anyone tell me if putting your application through the Application
> Builder has a real improvment on performance. Or does it just cut the
> size of the exe. down?
>
There will be some performance improvement due to the fact that debugging
information is turned off on your VIs. You can and may have already done
this in the regular VI Setup dialog, but if not, the app builder does it
for you. The second speed benefit will be that it loads more quickly since
the files are smaller and there is less stuff in the file that isn't loaded
to disrupt the file cache.
The first speed benefit is measurable, but depending on how many subVI calls
are made in your executable, it will probably be pretty small, and
again, you
can do the same thing in the development envi
ronment.
Greg McKaskle

Similar Messages

  • Report Generation Toolkit and Applicatio​n Builder

    I am going insane trying to work this out.
    I am trying to build an EXE program using Application Builder. The program uses the Office Report Generation Toolkit.
    I have tried including the dynamic VIs into the project, both from the Development machine and from the CD. I still have the same problem : the application does not start Excel. It is like the commands go into a black hole. There isn't even an error message.
    I have attached my report VI for you to peruse. Any help is appreciated.
    Brian Rose
    Solved!
    Go to Solution.
    Attachments:
    TestReport.vi ‏122 KB

    Yes, Labview 8.2
    Office Toolkit = 1.1.1
    I have tried many combinations of what files are included, from just the top level VI, to every VI in the heirarchy tree (a major pain). I am now trying to rebuild the project from scratch and see if that does anything.
    Brian Rose

  • Error message in applicatio​n builder in Build Applicatio​n.vi

    Hello,
    I'm trying to make an executable file but I recive the following error message:
    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
    Possible reason(s):
    LabVIEW:  The VI is not executable.
    Does anyboy know the reason for this message?
    Thanks. 
    Javier de Pablos

    Hello Jaime,
    I've tried to compile a very simple VI (there is only a while loop that executes nothing and counter is wired to an indicator.
    I've attached you.) and I've got the same error.  So the code or any dynamic VIs are not the problem.
    I've repaired the Application Builder within Control Panel > Add and Remove programs but I haven't resolved the problem.
    Javier de Pablos
    Attachments:
    Untitled.vi ‏13 KB
    gg.bld ‏1 KB

  • How to distribute the serial core only with my exe and DLL applicatio​n using the Labview applicatio​n builder 8.21. I'm not interested having MAX and other components installed on the customer PC and in the program menu

    Since Labview ver 8.0 and later, I am not very happy with the new way the project installer is managing the additional drivers such as Serial.
    With LV 7.11 the serial components was included in the cab file and was installed on the target computer in a specific directory. The size of the distribution was pretty small and well suited for compact distribution.
    My LV application use only the serial object and with LV 8.21, if I include the serial 3.2 component, I get an enormus file including max, visa ... and a lot of fucky component I do not need.
    To distribute my application, I just need, the runtime engine and the serial driver as it was with the version 7.XX
    Looking for clever advises from you gentlemen!

    Thanks Dennis for you input
    My problem is in fact very simple. 3 years ago, I developped a software suite for X ray generator; My company is selling such generator all over the world and our control panel software and DLL (for OEM integrator) is based on Labview professionnal development plateform.
    To drive our generator, we just need to transfer ascii data using the strandard RS232 port still present on most of equipments used in the industrial area.
    Until LV version 7.11, there was no problem to include serial component in my distribution with a very reasonable size and transparency for the end user.
    with LV 8.xx (preparing a new release), I'm very disapointed to see, my distribution is increased of about for 10 Mo to 180 Mo just because I increase the serial component.
    May I mix a previous version of the serial component with LV 8.21?
    Should I change my source to Visa instruction only and merge visa runtime only to my distribution?
    is there any simple serial example based on visa and distributed with th application builder?
    I will appreciate your help in order to optimize my distribution
    Pascal 

  • LV 8.6 applicatio​n builder creates an empty installer

    LV seems to create the installer O.K.  At least there are no error messages.  However, after I run the installer, the directory where the executable is supposed to be does not exist.  There are no error messages when running the installer.

    Nisar F wrote:
    Hi earl,
    I hope you are doing fine. Here is the link that tells you how to build an installer. Particularly pay attention to step 3 -5 to see if you have set up the correct settings for source file to include in installer. Hope this helps
    Best regards,
    And step 6 shows you how to build a shortcut.
    Ton
    Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
    Nederlandse LabVIEW user groep www.lvug.nl
    My LabVIEW Ideas
    LabVIEW, programming like it should be!

  • Error 7 applicatio​n builder invoke node

    I get this error when I tried to build an application. "Error 7 occured at Invoke Node in Dist read linkage.vi-> Dist Cmp Settings to Disk Hier.vi-> Dist Build App Image.vi-> Build Application.vi Possible reason, LabView: File not found.....and then NI-488 Non Existent board." Anyone knows why? I was able to build application just fine last night. But then when I tried to build it this morning, that's the error that I got. Thanks.

    Check the info in this link:
    http://exchange.ni.com/servlet/ProcessRequest?RHIV​EID=101&RPAGEID=135&HOID=5065000000080000001673000​0&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0&USEARCHCONT​EXT_QUESTION_0=Error+7&USEARCHCONTEXT_QUESTION_S=0

  • Applicatio​n builder error coder 21

    I get this error code when trying to build an application and include the visa runtime install files
    What can i do to fix this error
    CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFBuildDist_Build.vi
    Loading product deployment information
    Loading product deployment information
    Loading product deployment information
    Loading product deployment information
    Loading product deployment information
    Loading product deployment information
    Adding files to installer
    Validating...
    Copying files...
    Scanning files...
    Updating files...
    Build complete successfully.
    Done adding files
    Preparing to build deployment
    Copying products from distributions
    Copying distribution 'LabVIEW 2009, Media 1' from: \\dtads2\it_software$\Labview 2009\DVD 1 of 2\Distributions\LabVIEW\LabVIEW2009\ to: C:\Documents and Settings\brockmaa\Desktop\11164 Carnivore\builds\FVT1_4 test\My Installer\
    Copying distribution 'National Instruments Device Drivers - February 2010' from: C:\National Instruments Downloads\NI Device Drivers\Feb10\ to: C:\Documents and Settings\brockmaa\Desktop\11164 Carnivore\builds\FVT1_4 test\My Installer\
    Building deployment
    Copying setup files
    Setting merged database information
    Setting product information
    Setting developer part information
    Starting final build
    Validating...
    *** Error: An internal tool or library returned an error. (Error code -21)
    Error Messages
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper32.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-PAL' not found for part 'palSetup.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-PAL {79F90480-F2A2-463A-943C-29046520D6BC}.xml'.
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-PAL' not found for part 'palSetup64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-PAL {79F90480-F2A2-463A-943C-29046520D6BC}.xml'.
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-ORB' not found for part 'niorbi.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-ORB {F2D3406A-0A97-4EB9-9A09-F20A874C16F9}.xml'.
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-ORB' not found for part 'niorbi64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-ORB {F2D3406A-0A97-4EB9-9A09-F20A874C16F9}.xml'.
    *** Error Details:
    Error in MDF API function: _MDFBuildDist_Build
    Error List
    .\InputParser.cpp(365): InstallerError 120
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
    While validating input parts.
    .\InputParser.cpp(365): InstallerError 120
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
    While validating input parts.
    .\InputParser.cpp(365): InstallerError 120
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper32.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
    While validating input parts.
    .\InputParser.cpp(365): InstallerError 120
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
    While validating input parts.
    .\InputParser.cpp(365): InstallerError 120
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
    While validating input parts.
    .\InputParser.cpp(365): InstallerError 120
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
    While validating input parts.
    .\InputParser.cpp(365): InstallerError 120
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
    While validating input parts.
    .\InputParser.cpp(365): InstallerError 120
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
    While validating input parts.
    .\InputParser.cpp(365): InstallerError 120
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
    While validating input parts.
    .\InputParser.cpp(365): InstallerError 120
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
    While validating input parts.
    .\InputParser.cpp(365): InstallerError 120
    Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-PAL' not found for part 'palSetup.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-PAL {79F90480-F2A2-463A-943C-29046520D6BC}.xml'.
    While validating input parts.
    and so on

    Hi brockmaa, 
    It seems that the files it needs to include the VISA runtime are not being found on your system. Try re-installing the correct version of VISA you need from:
    http://www.ni.com/nisearch/app/main/p/bot/no/ap/te​ch/lang/en/pg/1/sn/catnav:du,n8:3.25.123.1640,ssna​...
    and try to build the installer again and it should be able to find the correct files.
    DylanC

  • Applicatio​n builder error 1041

    Dear All,
    I have a problem to build a application in Labview 8.5.
    It's the first time that I try to build this application in fact it's the first application every I try to build.
    I found the following problem.
     Authentication: "Error Code Database.vi is password-protected. Enter the password to acces the block diagram."
    I do not know the password for this file.
    The building errors details I get are:
    Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
    Error 1041 occurred at Invoke Node in AB_Source_VI.lvclass:Apply_VI_Properties.vi->AB_So​urce_VI.lvclass:Copy_SourceItem.vi->AB_Build.lvcla​ss:Copy_Files.vi->AB_Application.lvclass:Copy_File​s.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Bu​ild.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB​_Build_Invoke.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  Incorrect password.
    Method Name: Lock Stateet  
    When I start looking for the file that causes the problems I find that it is "Get File Type.vi" it's protected.
    This is an NI file and I do not know the password and I do not know why it is locked.
    The VI general properties of the file are:
    C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Utility\lvfile.llb\Get File Type.vi
    File revision is 78
    I tried to solve the problem as discribed in tread
    http://forums.ni.com/ni/board/message?board.id=170​&message.id=297099&requireLogin=False
    But that did not work for me. A build with a new file also gives the same error.
    So I tried something else in the Build specification there is a menu "source file settings". There is a selection about passwords
    You can choose 3 settings 1) No passord change 2) Remove password 3) Apply new password. I changed this setting from 2 to 1.
    And I can build the project now. So I change back from 1 to 2 and I should get the error back again. And I did not. How can this happen?
    What is going on?
    Thanks in advance

    Mike, you can't change the password if you don't know the old one. Why do you want to change the password? I do't wanna change the password. The application builder is asking for it and I do not have it. The same problem occured at thread http://forums.ni.com/ni/board/message?board.id=170​&message.id=297099&requireLogin=FalseIt looks almost the same but the solutions there did not work. The problem kept occuring.  So I tried someting else:
    In the Build specifications there is a menu "source file settings" for your project files. I only have 1 main.vi project file
    There is a selection about passwords for your source file settings. See attachment 3. You can choose 3 settings
    1) No passord change
    2) Remove password
    3) Apply new password.
    I changed this setting from 2 to 1.And I can build the project now. So problem solved.
    Then I changed back from 1 to 2 and I should get the error back again. And it did not.
    I do not understand why it works and I would like to.
    What is going on?
    Attachments:
    Authentication.JPG ‏13 KB
    VIPropertiesProtection.JPG ‏131 KB
    SourceFileSettings.JPG ‏52 KB

  • Applicatio​n Builder: error in building DLL from a VI

    I have a VI which I have been compiling into a DLL for use with Labwindows. Suddenly yesterday the build would no longer compile. Instead the error message (see attached picture) persisted all day no matter what I changed in the VI. Before the error message appeared, the Labview project window went blank for a moment, then showed some "C" code from somewhere, and then back to the project window. It's almost like something blew up in the compile process.
    I've tried all suggestions in the error message. Checked data types and names. I believed the VI is wired back to where it was. There is not much to the VI but it does reference some .NET assemblies.
    Thanks for any comment or help,
    Doug Wendelboe
    Attachments:
    VI-DLL-Pictures.zip ‏21 KB

    Hi Eriquito:
    Thanks for your response. I've included some snapshots of appropriate Ap Builder setup pages. My DLL is named "CVIMESQueryTray.dll". I had this compiling quite well up until a few days ago, so Ap Bldr didn't object then.
    See if you can spot something in my ApBuilder setup that I might be doing wrong.
    Thanks for your help.
    Doug Wendelboe
    (Hmmm.. I guess I can't attach more than three items, so I ZIPped them into one file).
    Attachments:
    ApBuilderPics.zip ‏154 KB
    ProjectFile.JPG ‏60 KB
    ApBuilderPage1.JPG ‏31 KB

  • Error when loading customer's applicatio​n build script

    I'm updating a program for a customer to include a module that we have developed. We're required to use an application builder script because of the way the VIs work.
    Anyways, when I attempt to load the build script for the LabView 6.1 application, eventually an error box comes up with the following message:
    Error 1 occured at Program Files:\National Instruments\LabVIEW 6.1\vi.lib\addons\_office\_wordsub.llb\_Word Dynamic VIs.vi - invalid path.
    Possible Reasons:
    LabVIEW: An input parameter is invalid.
    or
    NI-488: Command requires GPIB Controller to be Controller in Charge.
    I'm confused about the Program Files:\ syntax. Is this a valid reference? I can only assume so, as I believe they used this build script in the past. I'm currently working on Win2k, and I do not know what the customer's machine is running.
    Is there a particular Windows or LabView setting that would let this build script work? If not, is there an application build script editor that I can use to change the file reference?

    Yes it's a valid path, see attached screen cap of the exact path on my computer (except version 8.2).
    It looks like the target computer is just missing the MS Office toolkit, or the installation was not Typical. Tell the user to install the toolkit in the proper directory and it should compile.
    Message Edited by Broken Arrow on 06-04-2008 09:08 AM
    Richard
    Attachments:
    forum path pic.JPG ‏70 KB

  • "Add a dynamicall​y VI" in Applicatio​n Builder to prevent Error 1003 is no solution for a steadily rising amount of SubVIs.

    My VI calls SubVIs (all with the same connections) in a loop with one 'call by reference'. It works great in the VI but when I build an Application I receive Error 1003. After that I read in the KnowledgeBase when I build the Application I must add dynamically all the SubVIs I call by reference. Works fine at the moment but the amount of the SubVIs is rising steadily (approximately 10 per week) and there are many users all over the world of this application. So it is practically impossible and very uncomfortable to build a new application everytime the amount of SubVIs rises. There must be another solution maybe some kind of initialization, adding
    the paths of the dynamic called SubVIs programmatically???

    You do not have to include all the dynamically called subVIs in your build. If you look at the shipping example called Plug In Example, the dynamically called VsubIs are in a subfolder called plugins. In this example, the paths to the subVIs are created based on what files are present and which have the correct type specifier. The high level VI can be built into an executable. The plugins folder could also be included with one or two subVIs but once installed, new subVIs can be distributed separately and just put into the folder. The only trick is to make sure that the path to the plugins folder is correctly obtained whether the VI is run in development mode or as an exe.

  • Applicatio​n builder error creating

    After install Labview 9.0f2, no longer is possible to build application
    Solved!
    Go to Solution.

    Would you like us to continue guessing, or would you be capable of providing some details?
    Such as what the error is?
    What was the version of LabVIEW you were using?
    What toolkits you are using?
    Anything else you can think of?
    Remember, we don't have one of those nice troubleshooting scripts that call centers have.

  • Applicatio​n builder default control value

    I have a VI the reads a data file.  When I build an application and transfer the application to another computer the default directory is no longer valid.  Is there anyway to allow the user to establish a default directory for the file read on his computer or does he always have to go through multiple levels to find the file every time he restarts the application?

    There is an initialization file (projectname.ini) that is created with your application (build for the application). You can define your default locations there. Note, you will need to configure the builder to use your file.

  • Applicatio​n builder error 26005

    Hello All,
    When I try to build my application I get the following error:
    L'erreur 26005 s'est produite à Build Application.vi>>Dist Call Create Installer.vi>>Win Install
    Create.vi>>MSI DK Open.vi
    D:\TMNHe\Exe\TMNHe_Testeur_20090709\Installer.
    Raisons possibles:
    NMDK_OPEN_CAB_FILE_CREATE_FAILURE
    Can anyone help me?
    Labview and builder 6.1
    Solved!
    Go to Solution.

    A new installation of builder solved the problem. ?????

  • Applicatio​n Builder Source File Settings

    I've recently upgraded to the full version of LV 8.2 and purchased the license for the application builder.  On the "Source File Settings" tab I would like the program to not run when opened, and not to show the tool or scroll bars.  Although I've tried several different check, uncheck combination my final .exe alwyas has these options enabled.  I checked my original VI properties and it is not set to run at start up.  I'm not even sure what the "Value" highlight section is for.  My program is a simple temperature monitor and aquisition program with no sub-vi's.  What am I overlooking?
    Thanks.
    LabVIEW 2012 - Windows 7
    CLAD

    Hi MeCoOp,
    look at this post
    Ton
    Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
    Nederlandse LabVIEW user groep www.lvug.nl
    My LabVIEW Ideas
    LabVIEW, programming like it should be!

Maybe you are looking for

  • Table for output type of a delivery document

    Hi guys, Would you know where could I find the output type of a delivery document espcially after I posted a GI in Shipment? Basically, It should reflect in devlivery document. So I am not sure if I should look at the delivery tables or goods issue.

  • Scheduled report is failing to be triggered via email in SCOM 2007 R2.

    Hi All, I have this strange issue. I have created a scheduled report from the SCOM reporting. It is a default report which comes in SCOM, It is the Most common alerts available in the Microsoft generic report library. I also have the SMTP server conf

  • How do I create an image of our standard MacBook build?

    Hi, I've been set the job of creating a standard image for all our companies MacBooks. We currently have a build process, but this takes several hours for each MacBook and isn't very convienient. What I would like to do is install all the required so

  • SAP R/3 and BW reports

    Hi, One of our clients is wanting to know what all reports SAP R/3 and SAP BW can generate for an industry. It will be great if any of you can help us with some presentation/link/document where we will find relevant information (material of any infor

  • Need help with LCD projector

    I am new to mac book pro. Need to use for presentations - hooked up to LCD Projector. When connected, the projector only shows my wallpaper or a ppt slide show. What do I need to do to project other files or websites?