LabVIEW 2009 x64 and applicatio​n builder

Hi
My organisation has just got a site licence for LabVIEW so I have just installed 2009 x64.
My question is this:
If I build applications written using LabVIEW 2009 x64, will they only run on 64 bit computers? I would test this but both my computers are 64 bit machines. I have had a brief look through the build specs but there doesn't seem to be anything about 32/64 bit compatibility.
thanks.
J 
Solved!
Go to Solution.

Does this help?
http://digital.ni.com/public.nsf/allkb/71E9408E6DE​AD76C8625760B006B6F98
Q. Can I run an executable built with LabVIEW 64-bit on a 32-bit PC?
A. You cannot run the LabVIEW 64-bit Development System, Run-Time Engine, or executables on a 32-bit PC.
Q. Can I run an executable built with LabVIEW 32-bit on a 64-bit PC?
A. Windows can run 32-bit executables on a 64-bit PC. Therefore, the LabVIEW 32-bit Development System, Run-Time Engine, and executables can be run on Windows 64-bit.
Q. Can I have both LabVIEW 32-bit and LabVIEW 64-bit installed on the same 64-bit machine?
A. Yes.
Q. Can I build a 32-bit version of an executable from the LabVIEW 64-bit application builder?
A. There currently is not an option to create a 32-bit version of an executable from the LabVIEW 64-bit application builder.

Similar Messages

  • Favor to ask : can you open this labview 2009 Vi and save it for me in a Labview 8.6 readable vi ?

    Hi guys, 
    I have a favor to ask : May somebody would be nice enough to open this Labview 2009 VI and save it in a Labview 8.6 readable VI  ? You'll probably have some missing blocks cause I use specials ones but I don't want to have to re-make all the VI.
    Thanks you very much
    G.
    Solved!
    Go to Solution.
    Attachments:
    Control3.vi ‏29 KB

    notimperial wrote:
    Probably not the right place to do this, but could someone onpen this in labview 2010 and save it in a format compatible with labview 2009?
    Thank you in advance
    You are right we have a thread for this here.
    http://forums.ni.com/t5/LabVIEW/Downconvert-VI-Req​uests/m-p/1067229
    Here is your vi please use the downconvert thread next time.
    Tim
    Johnson Controls
    Holland Michigan
    Attachments:
    WFMreaderIII.vi ‏53 KB

  • Pb labview 2009 Number and string store data in file

    Hi,
    I m using labview 2009 in order to save data from instruments of mesure. My program generate Charts of string data that i would like to store in a file of table data. But when i read the file i don't see the digit after the digital point. So i forgot a part of the information which are very important for me.
    Futurmore before the instalation of labview 2OO9 the program was ok with labview 8.5;
    What can i do to solve this problem?
    Have any modification with labview 2009?
    Thanks in advance for your answer.
    Attachments:
    Image12.png ‏24 KB

    HI,
    In attachment file you will find the data before the saving operation in data file.
    We see in the file after the result. We have forgot all data after the decimal point, so we forgot a part of infortion that are very important in my application.
    Thanks in advance for your help
    Marc
    Attachments:
    AFTER.txt ‏1 KB
    before.txt ‏1 KB

  • Labview 2009 x32 and x64 installation error on windows 7 x64

    When attempting to install the evaluation version of labview installed by clicking the try labview for free link on ni.com, I am experiencing an installation error.
    the full error is shown in the attachment below, and is as follows;
    The NI VC2005MSMs x64 installation has failed with the following error.
    Error 1935. An error occured during the installation of assembly 'policy.8.0.Microsoft.VC80.OpenMP, type="win32_policy",version="8.0.50727.762".publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64"'. Please refer to Help and Support for more information.
    processor is an INTEL core 2 duo
    running windows 7 x64
    The above error occurs with both 32 and 64 bit versions. I belive I have installed this version of labview on this computer before.
    Thanks
    David
    Solved!
    Go to Solution.
    Attachments:
    labview_error.jpg ‏48 KB

    Why Does My LabVIEW Installation Fail With Error 1935?
    Also see this discussion

  • 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

  • Using RSLinx OPC with Labview 2009 SP1 and Getting Wierd Problem

    I have a small test system with 4 analog inputs and 4 analog outputs. Oddly, I can use the Labview Distributed Systems Manager and read the input (level) changes and stroke the analog outputs (valves). However, when I go into a VI, I can get the level readings (only the first time I enter, after that not), but can never stroke the valves. Looking at the shared variable setup in both the project I am using and the Distributed Systems Manager, I have them both set up the same as a PSP with the same OPC reference, although formerly the project used project-attached shared variables.

    Using the timed structure set at the same acquisition rate as the OPC interface corrected the problem.

  • Can i build an application with Labview 2009 for Windows 7?

    Hello
    i use Labview 2009 SP1 and the application builder 2009 SP1. If i install the application on win7 this message is display:
    Labview Run Time Engine depends on pruduct with upgrade code (...) version 9.0.301, language {} which is not in distribution.
    Solved!
    Go to Solution.

    Is this an issue with Windows 7 having both installation folders for 32 bit (C:\Program Files (x86)) and 64 bit (C:\Program Files)?
    I had an application built on an XP machine and installed on a Windows 7 machine which was looking for files in C:\Program Files when they were actually installed in C:\Program Files (x86) - because it was 32-bit application.  After installation I had to move the files from 1 location to the other to make it work.

  • Remote Panels and LabVIEW 2009

    Hello,
    I have updated my real-time PXI application to LabVIEW 2009 (Pro)  and I'm now trying to connect to it with remote planels.  I can only have one remote panel opened.  The second one gives me the "Remote Panels connection exceeds maximum numbers of licences"  The problem wasn't occuring in LabVIEW 8.5 and I have the remote panel license (unlimited) is actived in the license manager.
    How this can be resolved?
    Regards,
    Patrick
    Solved!
    Go to Solution.

    Have you transfered the license files to the controller since the switch to 2009?  There should be a .lic file under ni-rt>>system>>shared>>licenses on the controller.  Is that present on your system?
    Justin Parker
    National Instruments
    Product Support Engineer

  • Labview 2009 SP1 - Create exe option does not appear

    Hello everyone,
    I'm using Labview 2009 SP1 and I want to create a simple exe file (to run in the same computer that has labview or in any other  computer with the appropiate labview run time engine).
    I create a project with project explorer with the appropiate VI, everything OK for the moment, but when I right click on the menu "Build Specifications" of the project explorer I only have the options New and Help. If I click on New I only have "Source Distribution" and "Web Service (RESTful)" I would like to see the option Application and be able to create the EXE file.
    Anyone knows how can i create simple EXE files or make the option "Application" to be visible?
    Thanks for advance!
    Much thanks for your time and dedication!

    I guess you did not install the LabVIEW Application builder when you installed LabVIEW. When you do, it will allow you to create the exe and installer (You must be having a valid licence also).
    The best solution is the one you find it by yourself

  • Issues about labview 2009 applicatio​n builder

    first of all, sorry for my poor English ~~~i am not quite sure about whether i could make myself clear for you guys.here it is:
    SFX-ZIP archive is choosed as the file format for built-exe in labview 2009.when building any project into exe in labview 2009, you can always turn the suffix of the application file into zip. then use any compress-decompress software to open that file.shocked? right? yes, all the vis that used in your project are there. of course, you can decompress all the vis from the archive.although the block digram is removed during the building process, they still can be dragged into any vi and work perfectly. 
    this is so insecure both for the application and the source code.how about you?
    Message Edited by hunt978 on 05-10-2010 04:16 AM

    Double post

  • Getting Error 08 when attempting to build exe using LabVIEW 2009 (32 bit) and Windows 7

    Testing development platform on Window 7 vs XP. I received following message while building an executable using 2009 32 bit on Windows 7 machine. Same build will work on an XP machine.
    Error 8 occurred at Copy in AB_Engine_Copy_Error_Files.vi->AB_Application.lvclass:Copy_Error_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:  File permission error. You do not have the correct permissions for the file.
    =========================
    NI-488:  DMA hardware error detected.
    C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2009\errors\Internet Toolkit-errors.txt
    Any suggestions?
    Thanks

    For any who may be having this problem here is a little more information and what I did to get around the issue. (so far)
    First I tried a simple vi with a while loop in a project and made an executable build. This worked. I double checked on an XP machine the project that I was having problems with. The executable was built successfully. I changed back to the Windows 7 machine.  On the program compatibility trouble shooter I started the LabVIEW 2009 (32 bit) in the XP service pack 2 mode and selected run as administrator. The build was successful.
    Note: was logged in as administrator and program would build a simple executable in Windows 7. The executable that would not build had more complex code that included serial communication and calls to lvanlys.dll and nilvaiu.dll.
    This may not be a complete fix to the problem but at least in this one case it worked.

  • Potential Bug with LabVIEW 2009, Report Generation Toolkit, and MS Office 2003

    We have discovered an issue with the above listed software.  Specifically this pertains to Print Report.vi in the Report Gen palette.  Basically, we have discovered that with Office 2003 installed the VI will error out.  We've been using it in an executable, and the executable physically fails (and asks us to report an error to Microsoft).  With Office 2007 we don't have a problem.  We've tried building the examples into executables, and those work because they are printing HTML reports.
    Also, we have converted back to LabVIEW 8.6 and rebuilt the executable and installed and it works perfectly.  Its on the combination of LabVIEW 2009 and Office 2003 that seems to fail.

    yeah, we had seen that, and been told about it by another user.  we tried, to no avail.  we still have ended up having to migrate back to 8.6.1 to get the executable to run properly.

  • Help needed in adding custom About box in built applicatio​n in LabVIEW 2009

    Hello,
    Can anyone please help me add custom About box in built application in LabVIEW 2009? I had successfully built my application in labview 8.6, 8.5 and 8.2 before to include custom About box. However, when I tried the same method in LabVIEW 2009, it only showed LabVIEW 2009 About box rather than my custom About box.
    Here is what I did:
    1) Wrote an "About Application.vi" in the built VI folder;
    2) Included this "About Application.vi" in the "Always Included" section of Source Files in Application Build;
    3) Built the application;
    4) Ran the built application, the About box showed only LabVIEW 2009 about (attached a picture).
    You can see that on the upper left corner of the picture, there is my custom icon.
    Your help is greatly appreciated,
    Cathy
    Solved!
    Go to Solution.
    Attachments:
    About Box.JPG ‏34 KB

    Here is the link to download LabVIEW 2009 f2 patch:
    http://digital.ni.com/public.nsf/websearch/C3F88F3​596A164AD86257647006FB022?OpenDocument
    Thanks for the help,

  • Labview 2009 SP1 Installer build help needed

    Hello,
    First time posting here.  I have a rather large project that I recently converted from Labview 7.0 to 9.0.  I am able to build an executable and it starts up Ok but I don't know for sure if it works.  Since I couldn't build an installer, I copied the folder containing the .exe onto the targeted machine and installed Labview Run-time Engine 2009 SP1.  The executable then complains that it needs the full development version to work.  I am not too worry about this part at the moment, but if you have any pointers, please go ahead and post them.
    Ok, I have gone through a lot of posts on building and installer but it seems the one post that has something similar to what I experienced didn't get an answer.  Here's the Build Errors from the pop-up dialog:
    CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_BuildDevPart.vi >> NI_MDF.lvlib:MDFBuildDevPart_SetOtherProperties.vi
    Loading product deployment information
    Loading product deployment information
    Loading product deployment information
    Loading product deployment information
    Adding files to installer
    *** Error: An internal tool or library returned an error. (Error code -21)
    *** End Error Report
    *** Error: Windows SDK function returned an error. (Error code -12)
    *** End Error Report
    The build log file has slightly more info:
        [LOG ON]  Mon May 31 20:55:07 2010
    <<<MDFConfig_SetDeveloperLanguage>>> Language id: 9
    <<<MDFConfig_SetDistributionLanguage>>> Language id: 9
    <<<MDFConfig_SetBuildDir>>> Build directory: C:\HardwareTest\XXX\Release\Installers\Lab Test Suite 4.2.9 Installer - XXX
    <<<MDFConfig_SetBuildMode>>> Build mode: 1
        [NMDK BEGIN]  Mon May 31 20:55:07 2010
         Building developer part
    > Adding files to installer
    <<<MDFBuildDevPart_SetFileNames>>>
    <<<MDFBuildDevPart_SetDefaultInstallDir>>>
    <<<MDFBuildDevPart_SetUpgradeInfo>>>
    <<<MDFBuildDevPart_SetOtherProperties>>>
    > 
    > **************
    > *** Error: An internal tool or library returned an error. (Error code -21)
    Error in MDF API function: _MDFBuildDevPart_SetOtherProperties
    nmdkSetInformationalProperties returned error code 26024
    > *** End Error Report
    > **************
    > 
    Adding product dependencies to developer part
    > 
    > **************
    > *** Error: Windows SDK function returned an error. (Error code -12)
    Closing dist kit
    ***** About to begin MAXImportConfig:oMAXPartModifications...
    No MAX import files specified - nothing to do - returning.
    Error in MDF API function: _MDFBuildDevPart_Close
    Error in MDF::BuildDeveloperPart::Close.
    ERROR: Caught MSI Exception:
    <Unable to format error record.>
    MSI error code: 6
    > *** End Error Report
    > **************
    > 
        [LOG OFF]  Mon May 31 20:55:07 2010
        [MDF END]  Mon May 31 20:55:07 2010
         Closing MDF.
    I realize that I should post my project file but I can't do that until tomorrow.  From those 2 errors, can you tell me what the installer builder is looking for?  I have gone through all my dependencies and they look Ok at the moment.
    Thanks for you time.

    Hi Celeb,
    I had to help out on another project and finally only getting back to looking at this issue yesterday.  As you suggested, I went ahead and created a new project and created new build specifications (exe and installer).  I was able to properly build both items but won't be able to check out the executable til later this week.
    I noticed one thing about the project that Labview produced after converting the old *.bld file to a project file.  With the converted project, Labview adds unexpected installer destination folders into WindowsFolder in the Installer/Source Files/Destination View.  I thought I deleted them before but they seem to make it back (kinda hazy about this at this point).  My actual installer folder should only go into the WindowsVolume folder.  Anyway, on the new build spec, since I don't manually add the installer folder into the WindowsFolder, nothing get populated there and the installer is able to build properly.  This might have been the cause of my inability to build an installer with the converted project/build specs.
    I hope NI could add in more details into the build error messages.  As it is, it's really difficult to know why a build failed because there's no details in those messages.
    Thanks again,
    T.

  • Build Specifications gone with LabVIEW 2009

    I'm using LabVIEW 2009 and I still have the same problem as described in the following post (where all the answers were for older LabVIEW versions):
    http://forums.ni.com/t5/LabVIEW/build-specifications-gone/m-p/625815
    When I move a LabVIEW project from one PC to another, parts of the build specifications are gone. In the specification for the executable I have to redefine the start-up VI, the included files and the icon.
    Is this a known issue and is there a fix for it?

    Hello,
    this might be a corrupt project file. Does this only happen with this project?
    If so, then I'd suggest recreating the project and the build specifications on the original PC and trying to migrate it again to the other PC.
    Regards,
    Joseph Tagg

Maybe you are looking for