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

Similar Messages

  • 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.

  • LabView 2010 Applicatio​n Builder for EXE Always Included files are not Included

    In LabVIEW 2010 F2, When I am using the Application Builder to build an EXE file, I have listed 10 or so files to Be "Always Included". But when I Explore the directory where the EXE was built, those "Always Included" files are not there or in any subdirectory under the EXE file.
    This frequently makes my EXE file not work properly because important files are missing. I have to spend extra debugging time to find out the the cause of my problem is missing files that the Application Builder should have transferred "Always".
    Why did the Application Builder, when building an EXE target, not include the files that should be "Always Included"?
    Why does the Application Builder ignore these files specifications?

    Dennis Knutson wrote:
    The build does include files you select. Post an example project with a small VI and some separate files where this does not happen.
    No, it does not appear that all of the files that I listed in the "Always Include" list are copied during the Build process to the Build directory or any subdirectory under that.
    The Build Source Files.jpg file shows most of the list of the files that should be "Always Included". Notice the .VI and .ctl files that are listed
    The Build Directory.jpg file shows the file in the Build directory that were built.
    The Data Directory.jpg file shows the data directory under the Build directory and may include some of the files listed in the "Always Include", but not all of them.
    The other subdirectories under the Build directory were created by me and do not include any files that were copied during the Build process.
    So not ALL of the files that were included in the "Always Include" list were copied into the Build directory area as expected. ALL of the files that are listed as "Always Include" should be copied, if they exist. Those files existed when then were selected for the List and they existed at the time of the Build.
    I can not include an example project that demonstrates this. I am prevented from doing so by the terms of an NDA. You are going to have to take my word that this event is real and happens the same way every time. This information should be sufficient for someone to investigate why do not ALL of the files listed in the "Always Include" list are copied into the Build directory area regardless of the file type or contents.
    Attachments:
    Build Source Files.jpg ‏151 KB
    Build Directory.jpg ‏125 KB
    Data Directory.jpg ‏131 KB

  • Problem about Mac Os X 10.6.3 V.S Labview 2009

    hi,labview~
    i have some problem about Labview 2009.i saw the website of NI wrote the Labview 2009 is not support for Mac OSX 10.6.3,but i have already installed it (English system) in my computer successfully.
    anyway,i cant open the programs which are wrote by labview 8.5(Japanese system) .My labmate who use Labview 2009(Mac OSX 10.5) can open those programs.
    can anyone tell me the possible reason i cant open the programs?
    Thanks a lot! 
    PS i have already tried Labview 8.5 and 8.6(English system),but the problem cant be solved.... 

    Hi mofi, my name is Taiki from National Instruments Japan.
    I assume that the link you referred to is the one below, but as you stated, LabVIEW 2009 is not supported in Mac OS X 10.6 so even though you were able to install it successfully, NI cannot assure that it will fully function on your Mac.
    LabVIEW Support for Mac OS 10.6 (Snow Leopard) and 10.5 (Leopard)
    http://digital.ni.com/public.nsf/allkb/70F17A30DE7B865E8625737F006377F8?OpenDocument
    Since you mentioned that the VI files were able to be opened on LabVIEW 2009, Mac OS X 10.5, the actual VI files should not be the issue which leaves us with the possibility of the software environment.
    You also noted that the issue could not be solved on LabVIEW 8.5 and 8.6 but was this on Mac OS X 10.6 as well?
    If so, there is a good chance that this issue is due to the fact that LabVIEW is running on an supported OS and I would suggest trying opening the files on another different Mac OS X 10.5 system.
    Unfortunately, currently Mac OS X 10.6 is an unsupported OS for any version of LabVIEW so I can only suggest trying on a Mac OS X 10.5.
    Kind regards.
    Taiki Hoshi
    Applications Engineer
    National Instruments Japan

  • DocumentRo​ot in niwebserve​r.conf (LabVIEW 2009)

    I'm using the LV2009 built-in web server and trying to pick my way through building a stand-alone application.  So far I have done fairly well, but I have some questions regarding directives in the web server configuration file.  There seems to be some conflicting information in the forum regarding the path directives, so I'd like to pin it down here.
    The two posts I found that seem to relate to this directly are:
    http://forums.ni.com/ni/board/message?board.id=170​&message.id=434722#M434722
    http://forums.ni.com/ni/board/message?board.id=170​&message.id=393057#M393057
    So, can the path used for DocumentRoot be relative?  And if so, relative to what?
    Ideally, I'd like to have this relative to the configuration file (this seems to be indicated in the first post above).  However, it may be that the path is relative to the web server engine itself (as inidicated in the second post).
    Thanks for any clarification!
    James
    Solved!
    Go to Solution.

    Hi James,
    I believe that your first link to the post by NathanK is correct. He says there that "In 2009 all relative paths in niwebserver.conf are relative to the location of the config file itself." So the path can be relative, and relative to the path of the webserver.conf file.
    I think that the difference in his two posts is because the post in your second link is talking about LabVIEW 8.6, while the post in your first link is about LabVIEW 2009, along with information about the differences between the two versions.
    Regards,
    Stephen S.
    National Instruments
    Applications Engineering

  • 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 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.

  • 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.

  • 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

  • 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.

  • Error: "not enough memory to complete this operation" when building EXE + LLB in LabVIEW 2009

    Just upgraded to LabVIEW 2009 last week and can't build anymore.
    I am building and EXE with support files in LLB.
    PC Specs:
    -P4 3GHz
      -4GB RAM
    -Windows XP PRO SP2 
    - Windows is already enabled to use up to 3GB of virtual memory for applications. 
    - Performed a mass compile on all vi's.
    Not sure what else to try and will appreciate any suggestions.
    Thanks,
    Tavi. 

    This issue as well as a few others have been fixed in the LabVIEW 2009 f2 patch that was released today.  For more information, check out the following Knowledgebase for the list of resolved issues as well as download instructions.
    David_L | Certified LabVIEW Architect
    LabVIEW Tools Network | LabVIEW Tools Network Developer Center

  • LabVIEW 2009 Build Path Problem

    [Cross Posted to LAVA]
    I had some code that worked fine on my home PC, when I moved it to work, the exe would not build due to errors.
    The errors coming back weren't that good at explaining the problem
    Until I got this one:
    Look at the path in the error:
    C:\Users\Developer2\Desktop\User Group Meeting\LabVIEW 2009 new features\code\02 intermediate\01 build specifications\build executable file paths\dist\application 9.0\my application.exe\LabVIEW 2009\vi.lib\addons\_ICON Library\String\_icon_lib_string.llb
    That path is referring to a VI inside my executable!
    This may be a bigger issue that I first thought  
    So my question is:
    If a have a path inside my build that would be relative to the executable and LabVIEW needs to resolve it, could that process fail depending on where the exe sits in a folder hierarchy?
    I guess this could have happened before? but it would be more likely now due longer paths!
    Message Edited by jg-code on 08-26-2009 05:20 AM
    Certified LabVIEW Architect * LabVIEW Champion
    Solved!
    Go to Solution.

    Solution in cross post
    Certified LabVIEW Architect * LabVIEW Champion

  • LabVIEW 2009 program runs with no issues .exe does not

    Hello,
    We have been doing some new LabVIEW development.  We started turning them into executable.  Errors occurred during the build in a File I/O vi.  This was resolved by copying the diagram into a new vi.  This seemed odd given that it was the same vi.  Any thoughts on this?
    There are problems with the program operation once we create and run the .exe.  The vi runs fine.  Hum? Some of the issues are......  (1) some of the setup .vi for our test equipment no longer setup the equipment correctly (2) sub .vis that were set to show must be set in the vi properties of the vi instead of in the calling vi.  I've read that the executable run quicker than the vi.  ....most of our communication to instruments is through GPIB.  Are there any suggestions on how to control timing when using GPIB?
    THANK YOU!

    Why can't I run an executable created in LabVIEW 2009 and later, and how do I fix it?
    Theres a good KB article that should set you straight.
    Jeff

  • Labview 8.2 applicatio​n builder - installer deletes previously installed programs

    Problem Description :
    I've been developing with LabView for 8+ years and recently had to upgrade from 6.1 to 8.2 because of compatibility issues with LabView, MAX, DAQ and SERIAL. LabView had always been so intuitive and efficient, but that has changed to some degree sometime after 6.1 IMO.  I won't get further into that, but I am having several problems with Application Builder and particularly, with creating an Installer and installing test programs.  I haven't seen many posts on this subject so I assume I am doing something wrong.
    In 6.1, I could build a program and create an installer in minutes, and all in the same step - Click on Build and the installer was created. I could also locate my files anywhere I wanted. Unfortunately the process in 8.2 is no where as simple as one has to create a build and installer separately. So far, I haven't been able to distribute my installer files where I want them according to our internal procedures. The build portion works fine and I can locate my files as needed, but not so for the installer (at least I haven't figured it out yet).  The main problem is that I have some common DLLs that I'd like to locate in a common directory for all of my programs, but it seems like I'm stuck putting them in the installation directory of every program that I write.  Again, it is fine in build.  There doesn't seem to be any flexibility in changing the location of the files in the installer.  I did see a post somewhere that mentioned that DLL files must be located in the system directory if you don't want them included in the build or installation.  I would just like to install the dlls to a common directory and not include them in every installation directory.  Just like I did in LV 6.1!
    This is a relatively minor problem compared to what happens when I try to install the programs.
    I have five separate programs for which I have recently built and created installers with the limitations that I've described above. I can install one program on my machine and it runs properly. If I try to install any of the
    other four, they will delete the previous installation - all the files are deleted (they all have different names). What I think is going on is that the installer thinks that these five programs are the same and simply overwrites the previous installation. One reason I believe this, is because I tried an installation and it failed with the error message that there was already a higher version installed. The higher version it was referring to was almost certainly the one program I could install, but certainly not a higher version of the one I was trying to install (it didn't exist yet). After I uninstalled the one program, I could install any other four. It doesn't matter if I install on  the build computer or the target computer (ATE).
    What am I doing wrong?  Please help me to resolve this problem.
    I wan't the build and install files in the same exact location:
    Example of my five programs and the locations of build and install:
    C:\KIK2-LabView\Customer Name\Base Part Number1\Program1.exe.......
    C:\KIK2-LabView\Customer Name\Base Part Number2\Program2.exe.......
    C:\KIK2-LabView\Customer Name\Base Part Number3\Program3.exe.......
    C:\KIK2-LabView\Customer Name\Base Part Number4\Program4.exe.......
    C:\KIK2-LabView\Customer Name\Base Part Number5\Program5.exe.......
    The support files will also be put in the corresponding directories. The common files were supposed to go in the KIK2-LabView directory instead of copies in every installation directory.
    Is there something I have to do with the registry? In 6.1 it was all automatic.
    I hope there are simple answers to my problems, but I have yet to find them out. I have been able to find very little info on Application Builder, and nothing that is comprehensive.
    Thanks!

    Thank for the reply, Andy
    I have scoured the Help files and this forum which helped me to create the build and installer, but they didn't address any of the problems that I described in my post.  I tried to make sure that I exhausted numerous resources before posting and requesting help.
    I appreciate the response, but you didn't quite get to my most important problem - that when I try to install a program from the created installer, it overwrites my previously installed program.  Actually I have found the answer in a different thread. --->  http://forums.ni.com/ni/board/message?board.id=140​&message.id=16146.  My problem is that I cut and pasted all of my project files and made the appropriate changes specific to each new project.  If you don't create brand new builds and installers in these projects, you will create duplicate registry keys, even though all of the names, numbers, files, etc. were changed to be completely unique.  I opened the .lvproj file in notepad and found several registry keys to be the same; here is an example:
    <Property Name="UpgradeCode" Type="Str">{831013BF-9112-45AA-BF13-A13F08098841}<​/Property>
    All of the projects that I created by cut and paste (and edit) method had this same exact key (as well as other keys) which was causing the previous install to be deleted/overwritten or gave me the message that a higher version already existed.  Again, this happened even though all of the project data was completely unique after it was edited, including the project filename (of course).  Finally, I completely rebuilt my projects from scratch starting with "New Project" and voila, they now all install properly.  Obviously, none shared any of the same registry keys. 
    I don't know if this is something that was overlooked, but it is so much easier to cut, paste and edit projects when they are very similar.   Unfortunately I have found out the hard way that new build and install spec's must be created.  Is there a change that can be made to the Project File in LabView so that when certain information changes (like the executable file name) that new registry keys will be generated?  It is obvious that you don't want someone to accidentally install a lower version of the project over a newer one, but it would have prevented my work time loss (several days) and will prevent time loss for others in the future as well.  Could you at least consider allowing the developer to generate new keys like was available in LabView 6.1?
    Also concerning the location of files, I previously had done all of what you said and can locate the build files where I want.  However, in the Installer (Source Files Tab), when I create the folders in [Windows Volume], all of the files from the build spec are put into the SAME directory, regardless of where they were located in the build spec.  If I try to delete one file, all will be removed.  I can't place individual files where I want them to go in the installer (if they are a part of the build).  Example:  In the installer, I created the subfolders KIK2-LabView\Customer\UUT Base Part Number on the [Windows Volume] directory and set the UUT Base Part Number as default.  I want most of the files to go into the default directory, but a few of the dependent dll's should go into the KIK2-LabView folder as they are common to many other programs/projects.  In short, I don't need or desire 50 copies of these dlls on my ATE.  I was able to locate the installer files anywhere in LabView Pro 6.1, but so far I can't figure out if this is possible in 8.2.  It would appear that it is not.
    Thanks,
    John W.

  • LabVIEW 2009 build memory usage exceeds Windows limit

    We have a large application that builds without problems using 8.6.1, but failed to build using LabVIEW 2009 with the error "Not enough memory to build this application".
    We solved the problem by adding the parameter /3GB to the Windows XP boot.ini file. This increases the available memory for a Windows XP application from 2Gb to 3Gb.
    It appears that LabVIEW 2009 uses more memory during the build process and, in our case, this took it over the 2Gb limit. 

    We are also facing the same problem...
    can National Instruments help us  ??????
    Following error is occuring while creating exe.
    "Build was unsuccessful
    An error occurred while saving the following file:
    D:\BIS_Main_2009_V3.XY\branches\BIS_Main_2009_V3.6​1_Trans\User Interface Panels\Inspection.vi
    Invoke Node in AB_Source_VI.lvclass:Close_Reference.vi->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_Build.lvclass:Build_f​rom_Wizard.vi->AB_UI_Frmwk_Build.lvclass:Build.vi-​>AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB​_Item_OnDoProperties.vi.ProxyCaller
    <APPEND>
    Method Name: <b>Save:Target Instrument</b>"
    Please suggest!!!

Maybe you are looking for