Application builder adds additional select instr.lib folders

Hi,
When I build my application, the Application Builder decides that it should include additional directories instead of the default files (data directory, .aliases, .exe, and .ini files). The additional directories include files that are named the same in various instr.lib's but are in different libraries, i.e. Close.vi or Initialize.vi. In my project explorer are there no unresolved dependancies. Does anyone know why this may be happening?
I just marked out the company name in blue if you were wondering.
Solved!
Go to Solution.

What version of LabVIEW are you using?  If you are using 2009 or above, there is an option to use the 8.X format for the executable.  It is one of the advanced options in the build specification.  You do NOT want to do that.  In the 8.X format, the VIs are saved in the executable as a flat directory.  This means that any VI that was named the same, regardless of library association, would conflict.  This would cause those libraries to be saved outside of the executable.
If you are using the newer format, the executable keeps a directory hierarchy, just like a zip file.  So you won't have the name conflicts in that instance.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Similar Messages

  • Add additional selection fields to RPUAUD00- Logged changes in infotype rpt

    Hi,
    I'am trying to add additional selection fields to Logged changes in infotype  report and was wondering if this can be done through customization instead of creating a copy of the std report to add the additional fields?
    Thanks

    Hi Ajay, The requirement is to add fields like personnel subarea, op code for reporting purposes.
    Thanks

  • VKM4 add additional selection fields

    Hey guys,
    is there a way to add additional fields to the transaction screen without modification?
    I want to do a search for those orders which has set the customer CMPS0, CMPS1 etc.
    thx,
       Ming

    hi,
    can you share how actually u do abt it, which program to change, how to add it in?
    thanks.

  • Custom icon in application builder

    I am trying to create an executable with custom icon using Application Builder in LabVIEW.
    I converted a .png image to .ico for the icon, but when I select that .ico file as a custom icon, I get the following message:
    "The selected file doesn't contain all of the needed icons. Without them, your application will show an incorrect icon in some views. 
    Missing icons:
    32X32, 16 color
    16X16, 16 color."
    Any comments\suggestions on how to get custom icon would be appreciated.
    Thanks.

    It's possible that you don't have both 16x16 and 32x32 icons in 16 bit color. When you convert the .png to an .ico, see if there is an option to convert into necessary ico images that you need.
    As a way to double check this without using application builder, load the VI : <vi.lib>\Platform\icon.llb\Read Icons for Application.vi
    It will show you the different icons that are read from the .ico file.

  • Application builder and dynamic class VIs name collision

    I'm, using LabView 8.6 and I'm trying to make executable file. 
    The application builder returns warning:  
    "LabVIEW prevented a file name collision during the build. Duplicate file names cannot be copied to the same destination. You can rename files as part of the build process to avoid name conflicts."
    ...and no executable is created.
    I'm pretty sure the warning comes from the fact that I use dynamic class member VIs, that are by definition have to have same names in both parent and children.    
    The following link (http://zone.ni.com/reference/en-XX/help/371361E-01/lvhowto/caveats_apps_dlls/) says " If you don't rename the files, Application Builder moves the files to different folders for you to avoid a filename collision.", but no folders are created.
    Any help here? 

    Hi,
    If you have a parent class and one or more child classes, during the build LV will create a folder for each class with a conflicting VI.  The offending VIs will be dumped in their respective folders, resolving the conflict.  For what it's worth, I've used dynamic dispatch VIs several times in executables in LV 8.6 without seeing the issue you're reporting.
    My only advice would be to:
    1) make sure that you haven't somehow put two VIs of the same name in the same class (not even sure that's possible).
    2) make sure you aren't renaming a VI during the build and creating a conflict
    JasonP - CLD

  • Add new selection in MRRL transaction

    A requirement to add additional selection field in screen shipment completion date ( vttk-daten ), how can i do this

    Hi Dattaraj,
    Go to se38 -> RMMR1MRS(program for MMRL) -> display
    Check for
    ENHANCEMENT-POINT rmmr1mrs_02 SPOTS es_rmmr1mrs STATIC.
    Create a spot...click on the spiral icon..screen changes..place cursor on ENHANCEMENT-POINT keyword of the spot mentioned...righ click -> "ehhancement implementation -> "create" -> a table control comes -> at the bottom "CREATE" button to be clicked" ...give a name and text in customer name space and save -> select the name in the table control ..you will get a space where code can be written
    Write your select-options code here..it will come on the screen
    Although you have added it here..you need to filter the same somewhere..search the program for an enhancement point  where a code can be used to filter the data before displaying on the screen
    What is mentioned above is a sample for adding to first block..if you need to add elsewhere search for the correct enhancement point to create your code....
    Reward if helpful
    Regards
    Byju

  • Additional selection criteria for RHECM_CREATE_COMP_PROCESS (create compens

    Dear All,
    There is a requirement to add additional selection criteria for  RHECM_CREATE_COMP_PROCESS.
    Compensation Plan needs to take several optiions rather than a single option.
    Incentive Plan Type to be added as additional selection criteria
    Do we need to copy the standard program and then modify it or there can be some other way out for it.
    Thanks and Regards
    Shraddha

    have checked out the SDN forums quite throughly and have come up with a couple of questions/solutions.
    1) Copy the program into Z-name space and add in the code
    Question: Where to specifically add the code, the program is huge with multiple enhancement points being seen in the code.
    Can someone please guide me where I can change the displayed records, point where iI can append data or change the internal table being sent for ALV display.
    <b>---> U have to find out , where /how  they defined Selection screeen , final output they are displaying.</b>
    2) Make changes in SPRO>Define field selection for material document list.
    Question: The required field is not present within the listing, It does give the option to make new entries, but I have to specify a program/table and field.
    If I create my own program to get the details and display onto an ALV Grid, will the program be called when I make selections on that requisitioner field?
    <b>---> lot of work to do</b>
    3) This is text copied from a thread, I have lost the link to it.
    Create a Z report that is a copy of the selection include of the standard selection screen include with the additional selection criteria.
    - Export the extra selection criteria value to shared memory.
    - Submit the standard VL10G program with the selection sets.
    - In user exit (depends on which field needs to be checked), import the extra selection criteria value back in and filter the selected data set.
    Could someone please guide me if it is possible to do the above within RM07DOCS, and a little more detail on how to go about it?.
    <b>Better Options --->try to get the logic of MB51 , then do changes which are required.
    most of data , u will get it from MSEGMKPFMARA+MBEW.</b>
    revert back in case of any other issues.
    Regards
    Prabhu

  • What is the best way to add a large number dynamic VI's in the application builder?

    Is there a way to add all the VI's in a directory tree or library file as "Dynamic VI's" in the application builder (7.1 on Windows XP SP2)?
    Thanks,
    Mark Moss

    LabVIEW 7.1: From what I can tell, you can only add dynamic VIs one file at a time, while for support files, you can add entire folder contents.
    Have you considered uprading to LabVIEW 8.0? Things like this have been improved dramatically! You can keep all your dynamic VIs in a project folder, then add it to the build specification in one click.
    LabVIEW Champion . Do more with less code and in less time .

  • How do I add a selection screen parameter to get a application server file

    Hi All..
    Can you please suggest how can we add a selection screen parameter to get a application server file ?
    Thanx in Advance...
    Regards,
    Deepak

    <b>Parameter def :</b>
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 02(30) text-005 FOR FIELD p_xlfil.
    PARAMETERS: p_xlfil LIKE rlgrap-filename OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    <b>Browse</b>
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_xlfil.
      PERFORM ws_get_filename USING p_xlfil.
    FORM ws_get_filename USING p_xlfil.
      CALL FUNCTION 'WS_FILENAME_GET'
           EXPORTING
                def_path         = 'C:'
                mask             = ',Excel,*.xls,All,*.*.'(100)
                mode             = 'O'
                title            = 'Title'(101)
           IMPORTING
                filename         = p_xlfil
           EXCEPTIONS
                inv_winsys       = 1
                no_batch         = 2
                selection_cancel = 3
                selection_error  = 4
                OTHERS           = 5.
      IF sy-subrc NE 0.
        CLEAR p_xlfil.
      ENDIF.
    ENDFORM. " WS_GET_FILENAME
    Regards
    <b>Oops i did not read "application server"</b>
    Use FM F4_FILENAME_SERVER and not F4_FILENAME/WS_GET_FILENAME.
    Message was edited by:
            Raymond Giuseppi

  • [ OIM 11gR2 PS1 ]How to add additional field on Application Instance Form ?

    Hi,
    In our scenario we have Disconnected applications in OIM. AI (Application Instance) form and PD editing is created by OIM.
    We want to add additional field in AI form.It is visible in back end. But,its not visible in OIM admin console for admin and as well for end user.
    Is there any property related to form field in AI ,where we need to make changes to make it visible ?
    Instance used is OIM 11gR2 PS1
    Thanks,
    RPB
    Edited by: RPB25 on May 29, 2013 9:46 PM

    I was able to resolve this issue . we need to click on "regenerate view".

  • Where do I find the VISA installation drivers to add to my application builder for my LabVIEW app?

    I need to add the VISA installation drivers to my LabVIEW application builder, but I don't know where to locate them. (I found the instructions on adding the drivers, but it didn't tell how to find them: http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/e09ba0e2f31d304f86256a640070058e?OpenDoc ument)

    The following webpage contains the NI VISA drivers that you can download:
    http://digital.ni.com/softlib.nsf/display?ReadForm&lookup=NI-VISA&view=current&node=132060_US
    Chris_Mitchell
    Product Development Engineer
    Certified LabVIEW Architect

  • How to add visa usb support to the application builder?

    Is it possible to add VISA USB drivers to the application installer?
    www.xinstruments.com
    Custom Software for Industrial Automation
    www.hdrconverter.com
    Picture processing made easy

    I'm afraid you can't do that. The LabVIEW 7.0 application builder only supports adding the VISA serial port driver to the application builder installer.
    You will have to install the VISA support for USB separately by using the VISA 3.0 runtime installer.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Build installer for lvlib for LabVIEW instr.lib folder

    Dear.
    It might be trivial.
    I build an .lvlib.
    What I want now is to make an Istaller.
    The installer should install the vilib into the instr driver directory of the current LabVIEW Version.
    I'm using LV 2011.
    The installer always wants to install the files into 'Program Files' folder.
    So the question is:
    How do I have to proceed?
    I want the complete vi and controls hirarchy including dir.mnu files to be installed into the instr.lib folder.
    Regards
    Martin

    This is a prime canidate for VIPM.  You can use the free version to build the package.  The best part of using VIPM is that you can "install" it on every version of LabVIEW you have installed (that is it compatable with, of course).
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • How to add third party dll in our installer using application builder?

    Hello friends,
    I have one application (VI) which is using some third party dll of protocol and now I want to make a installer which should install dll along with application exe. Please suggest the way ..
    Thanks
    Solved!
    Go to Solution.

    Hi,
    I placed it in project file and included it in category of "Always Included" in exe creation. Then after i created installer with needed NI drivers. But this installer didn't registered the dlls in project file. I registered it manually using regsvr32 command..
    Any help to do it automatically during installation..
    To brief my words, I need help to understand the process of third party dll registration during installation of installer created by application builder..
    Thanks

  • How to package instrument driver in the user.lib or instr.lib directory

    Hey guys,
    I currently am using bunch of instrument drivers in my project.
    In the VI form it works fine, but I noticed that once converted to an executable,
    there are errors regarding the DLL that the drivers are calling.
    Apparently the driver VI check if its being called in an VI or executable based on the current directory.
    I dont think this is good/correct programming to begin with... but anyways since this driver is
    saved in the instr.lib directory of LabVIEW, when I call it from the executable the default path becomes
    XXX.exe/1abvi3w/instr.lib/.../.../VI above.vi
    I saw this post  which talks about how vi's in instr.lib and user.lib will get the path 1abvi3w in an executable but never talked about how to deal with it.
    so my question is can i solve this problem smoothly without copying the entire driver.lvlib into my project and
    editing the VI above? i am fine with creating wrappers for driver vi's but would to like to avoid editing the driver vi's themselves.

    doradorachan wrote:
    I dont think this is good/correct programming to begin with...
    I don't disagree, but there is a reason this code was written like that (you might note that it doesn't actually work) - before 2009, EXEs were built as flat directory, so stripping twice would bring you to the folder. Because of the addition of libraries, where different files have different names, this was no longer possible, so 2009 builds the EXE as a zipped hierarchy of folders, which is why the check for a folder succeeds even inside the EXE.
    There are a couple of things you can do:
    Replace the VI path with the Application Directory primitive. This is designed to function differently in an EXE. Understandably, you don't want to do that.
    Check the 8.x checkbox in the advanced page of the build settings. This will make the code work correctly, but if there's LVOOP code with VIs of the same name anywhere, it will create extra folders that you need to move around with the EXE.
    Add the driver to the project (just the lvproj, don't actually copy the files) and then set an explicit destination in the build for its VIs as an LLB in the data folder. This will place the driver VIs in an wLLB, which is external to the EXE and should then strip correctly. I can't say I have much experience with this, but I'm assuming it should also work with code that was originally in user.lib. This is probably the cleanest solution in terms of number of files because you only have one extra file.
    Try to take over the world!

Maybe you are looking for