Application builder developer toolbar

Hi,
I don't want to have the developer toolbar (Edit application,edit page 1,new, session...) when i log in to my application.
any ideas?
kind regards
couse1

Zed - Search this forum for "developer toolbar" and find this answer, including the method of changing the application's Status attribute (application attributes) from Available with Edit Links to Available.
Scott

Similar Messages

  • Developer toolbar has disappeared

    Using Apex3.2 I have developed several applications. When logged in as a developer then running the application the developer toolbar appears at the bottom, as it should. But on one application it no longer shows. I don't know what I did to make it disappear, or how to get it back again. The problem is that as well as making further development awkward, I now cannot customise an interactive report and save it as the default. Any ideas on how I can get the developer toolbar to work again?

    Hi,
    Check from Application definition that status is "Available with edit links"
    http://download.oracle.com/docs/cd/E14373_01/appdev.32/e11838/bldr.htm#sthref307
    Also, have you set cache for pages ?
    http://download.oracle.com/docs/cd/E14373_01/appdev.32/e11838/bldr_pgs.htm#sthref626
    If I recall correctly developer tool bar not show for cached pages. I may remember wrong.
    Br,Jari

  • Missing Developer toolbar in new application

    Hi,
    There are several developers in my team and one of them cannot see the developer toolbar in a newly created application while others can see it. Any ideas on what might be causing this? We are in version 4.2

    You can only see the developer toolbar when you start the application in the same browser window (different tabs will work) as the APEX Builder environment or from the APEX Builder environment.
    So check whether the developers use the same way of opening up the application...

  • Display Bug in LV 8.20 Application Builder

    There seems to be a minor bug in the displaying of the "VI Settings" in the application builder for LabVIEW 8.20.
    The problem is in an executable build spec, in the "Source File Settings" category.
    Select a sub VI in the tree, then uncheck the select box for the "Remove Panel" property. Now select any other VI in the tree, then go back to the one you unchecked the "Remove Panel" box. You should see that the box is now checked.
    If you don't do anything else and just select "OK, then go back into the build spec, you'll see that the property was correctly saved as unchecked. So it looks like it's just a display problem.
    I've made sure the VI I try this with does not use any property nodes and it is not marked as a dynamic VI. I can reproduce this on two machines running Windows XP Pro SP2 and LabVIEW 8.20.
    Ed
    Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
    Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

    In addition to Ed's
    comment, I would like to say that this unexpected behaviour is not
    always appearing. I have just seen following while editing this text :
    I have unchecked the Remove Panel box for all the UI VIs (all are
    located in the same directory). When scrolling through the different UI
    VIs in the Soure File Settings, the box was unchecked for all the VIs.
    Without closing the Source File Settings window, I switched to
    Developer Zone and switched back to the Source File Settings. For some
    UI VIs, the Remove Panel box was checked. I closed the window and
    opened it again, the box was unchecked again for all the UI VIs.
    But I have also encountered the case that when scrolling through the
    VIs to try to uncheck this setting for all of them, it suddenly appears
    checked again for a VI for which it was unchecked or unchecked for a
    before checked VI.
    You finally end with a very unclear situation and it may be that the
    Remove Panel is really checked for some VIs. At least, in some cases,
    the built EXE could not run because of missing front panels. I can't
    remember the exact error messages when running the EXE but they
    mentionned the name of the VI and something about missing ressources. I
    opened the .lvproj file and noticed that the "Remove Panel" property of
    these VIs was set to TRUE. After modifying these settings and
    rebuilding the EXE, it ran as expected.
    In development, I
    normally uncheck "Allow user to resize window" of the UI VIs because
    this setting can unfortunately not be changed when configuring the
    executable. In the "Source File Settings" I uncheck all options of "Use
    VI Setting" for these UI VIs and I only check "Auto-Center" (all VIs)
    and "Window is Modal" (some VIs).
    There is another problem with the application builder that I would like
    to mention. For (at least) following settings, the development settings
    of a VI will not be overwritten by the Source File Settings when
    building the executable :
    - Window has title bar
    - Show Menu bar
    - Show Toolbar
    - Show Scroll Bars
    This is also very annoying because you will need to change these
    settings in the development environement in order to get the expected
    appearance in the executable.
    LV8.2 English / WXP SP2

  • Virtualize IE6 including Internet Explorer Developer Toolbar

    I tried to follow this thread http://forums.novell.com/novell-prod...h-plugins.html
    to virtualize IE6 including Internet Explorer Developer Toolbar
    As a result IE6 contains Internet Explorer Developer Toolbar button but it's not work on Win 7 machine.
    I think settings shared with IE9 somehow and it's not work, or what it can be?

    With ZAV 9 we have another option available:
    When you snapshotted the Internet Explorer Developer Toolbar, was the "Internet Explorer Snapshot Compatibility Mode" option enabled? This can affect how the snapshot turns out and should be enabled anytime a component will hook into IE.
    Have you tried building the virtual IE6 by having ZAV scan the system for installed applications? That might be worth a shot to get this working in Windows 7.

  • Where is my developer toolbar?

    Hello,
    Since I exported my application ("Run and build application") I don't see the developer toolbar. It seems that it is gone from all pages. I really don't understand what is going on. Anybody an idea?
    Regards,
    Jacob

    Hello,
    Silly question, but you are logging into the Application Builder interface aren't you? You will only see the developer toolbar if you login as a developer to the Application Builder.
    If you are logging into the App Builder, then we'll need more details like -
    1) Which browser are you using
    2) Are you using your own custom page template
    John.
    http://jes.blogs.shellprompt.net
    http://www.apex-evangelists.com

  • Application Builder and Closing

    Hi
    Already, another problem has arisen. I have developed a simple VI with no big thing inside. I am using an event structure for handling button presses. To quit my application, I have one button, labeled Quit (who would've guessed) which quits the application. I simply wired that button to the quit terminal of the event structure (ok, to the quit terminal of the while structure around the event structure).
    I have also built this application with  the Application Builder into a .exe file. I managed to get that Run/Pause buttons away. by checking the appropriate checkboxes inside AppBuilder. But now, what happens is as follows:
    * I quit my application by using the red X of the window - everything closes down fine, the window disappears *perfect*
    * I quit my application by using the button - the program stops, but the run button appears.
    How can I avoid that behaviour?
    Thanks for your advice

    There's a function in Application Control which is used to close LV once everything's done executing.  Be careful when using it while developing, as it will close all open vi's.  Granted you get the option to save them, but it's annoying nonetheless.
    See the attached image
    Message Edited by Novatron on 07-10-2006 11:17 AM
    Attachments:
    Quit.jpg ‏4 KB

  • After installing an application that was created using the Application Builder

    After installing an application that I created using the Application Builder I get this error if I try to run " ANY " LabVIEW App's that I have built. "Executable Version 7.1.1 doesn't match Resource File 7.1. Check your configuration."
    The way that I tried to fix this is to reload LabVIEW 7.1 and DAQmx 8.0. I am using two NI-6528 switch cards.
    After I reload LabVIEW and DAQmx I can run my applications but as soon as I install one on this development machine the error begins again.
    The executable that I built works fine on the development machine and any other machine that I try it on but it appears that the Run-Time engine 7.1 becomes corrupt after I run setup.exe for the newly created application.
    I have built numerous Installers, setup.exe's in the past without this error. Just this latest one caused this problem to start.
    I can NOT upgrade to 7.1.1. I am doing work for many different sections of this factory and I can not force them to upgrade. I've asked. Others supply code for the same machines using LabVIEW 7.1.
    I am stuck creating executables and manualing moving the correct files to the target machines.
    What can be done?

    No. The KB article was talking about a machine with 7.1.1 installed. I have LabVIEW 7.1 installed.
    The machine that I am having trouble with is my development machine. LabVIEW 7.1, DAQmx 8.0.
    If I build the executable all is fine. I can still run old executables including the one I just built.
    If I create the installer all is fine. I can still run old executables including the one I just built.
    When I install the app on my development machine the corruption occurs. I can " NOT " run old executables including the one I just built. The subject error pops up.
    I have not moved any executables to the other machines yet. I don't want to corrupt others.

  • Application builder-Office report generation toolkit

    Hi,
    I remember there was a trick to get the executable work with different
    versions of Microsoft office but I cannot find it now. The problem it to get
    the exe work with some other office version that it was made. I use LabVIEW
    7.0 - 7.1 and Report generation toolkit 1.01 for Microsoft office. Was that
    possible?
    Thanks Eki

    Eki,
    When you use the Report Generation Toolkit to build a stand-alone application with the Application Builder, you must add _Word Dynamic VIs.vi from _wordsub.llb and _Excel Dynamic VIs.vi from _exclsub.llb as dynamic VIs. These two VIs contain subVIs that are called dynamically by the high-level Report Generation VIs. I believe that if you grab these VIs from the (desired office version part of the) installation CD instead of from the development machine, then everything should work.
    Zvezdana S.

  • Lost Developer Toolbar after upgrade from 4.1 to 4.2

    After upgrading from 4.1 to 4.2.1.00.08, we have lost the Developer Toolbar.
    Have others run into this with the upgrade or fresh installation of 4.2.1?
    If so, what suggestions are there for fixing, short of reinstallation mentioned in this other thread:
    {message:id=10692572}
    Following the guidance there to look at the instance ID and other preference settings, I compared our three instances. The two that are not having the problem are both at 4.2.0.00.27.
    Here are the preferences that exist on our other instances but are null on the problem instance:
    APEX_4_1_0_PATCH_12920544
    APEX_4_2_0_PATCH_14777994
    APP_EXPORT_TO_DB_ENABLED
    HPROF_DIRECTORY
    INSTANCE_ID
    MOBILE_DEVELOPMENT_ENABLED
    PRINT_SVR_HOST
    PRINT_SVR_PORT
    PRINT_SVR_SCRIPTI have asked our support team to review the upgrade log. Re-installation from scratch is an option.
    Any advice is welcome.
    Skip

    Thanks, Joel.
    You inspired me to take a closer look, and look beyond the upgrade.
    After the upgrade, my application passed a superficial checkout. Later, I exported my application and in the export file, the Instance ID was not NULL. I had not noticed any problems with how APEX was working.
    The problems of the missing Developer Toolbar, Instance ID = NULL, and a new one, did not occur until I removed my application and tested a clean installation of the workspace and application. This is the sequence of events. The immediate triggering cause is clearly one of the following:
    1. Deinstall application (ID 820) from APEX 4.2.1.00.08 instance, running 11g (11.1.0.7.0).
    2. Remove workspace (PVA_AH9_R12)
    3. (drop the parsing schema, xxpva, and related tablespace)
    4. (create tablespace and schema user, xxpva)
    5. Import workspace (PVA_AH9_R12) from an APEX 4.2.0.00.27 instance.
    6. Import application (ID 820) including supporting objects from an APEX 4.2.0.00.27 instance, running 11g (11.2.0.1.0).
    The next day I noticed the Developer Toolbar missing problem, and found that Instance ID is NULL.
    Also, after Exporting an application in Database format, I cannot download the file from the Export Repository. When I click the filename link, I get 'Access Denied' instead of the normal download dialog.
    Does this suggest anything else I should look into?
    Do you think I should post this as a new problem/question with more detail about the sequence of events?
    Skip

  • Error message "VI is not executable"! Need help with Application Builder

    Hello,
    I have a problem with an application, built with the Application Builder. I have read some threads about the problem I have, but I still don't know a solution.
    When I run my front panel from LabVIEW, everything is good. So, now I created an application (and an installer) to be able to run it on other PCs as well. This application does not work. Everytime I start it on my PC, I get the error "VI is not executable. ...". I read in several forums solutions for this error, but I cannot fix it! I've changed my properties for the builder, but with no success. Perhaps, anybody has more ideas, what's the problem.
    To get a better idea from my project, here a little description of it:
    In the block diagram there is a while loop which is continuously runned. In this loop I only set some properties for the layout of the front panel, such as decorations which will be hidden/shown and changes of colours of indicators... For the rest, it waits for a click on the button "Start" in the front panel. After that, a DLL is called to communicate with a USB device. Some measurements are carried out and the DLL is closed. I hope, you can get a global idea from my block diagram...
    I use LabVIEW 8.5, the DLL is a third-party DLL, which we wrote on our own. But I think the DLL works properly, if it is called from a C# application it works and it works, too, by calling it from LabVIEW when I am in development mode.
    It's a project for university and I'm just a beginner in LabVIEW, so I don't have so much experiences in it, but I think i improved my knowlegde about LabVIEW very well in the last weeks!
    So, i hope to get an answer soon (the deadline for the project is not soooo far away )
    If you need more information, please let it know...
    I would be very grateful if there is someone with a working solution...
    Kind regards from the Netherlands,
    Sebastian

    Sebastian,
    Your architecture makes it very difficult to debug this and other problems.  Does the error message mention which VI is causing the problem?  It is very important to wire your error clusters everywhere.  In LabVIEW, when a node throws an error (Error.Status = T), future nodes do not execute.  At the end, place an error cluster indicator that you can see on your front panel.  When an error posts, you can right click the indicator (even in a compiled application) and select "Explain Error".
    This is a start, but you really need to push this into a queued-state machine before this gets any more complicated.  As it were, if anything in your loop hangs, your whole application hangs.  See attached for a queued-message handler (not advisable for actual applications, but you get the point.  You would want to have a type defined enum in lieu of strings, and shared data between states differently, etc.)
    -Jason
    Message Edited by LabBEAN on 01-20-2009 08:36 AM
    Certified LabVIEW Architect
    Wait for Flag / Set Flag
    Separate Views from Implementation for Strict Type Defs
    Attachments:
    State Machine.vi ‏18 KB

  • Application Builder: What is the significance/function of "page sequence"?

    Because we are always pressed for time, I have developed the nasty habit of glossing over things that may be opaque to me, with the mental reservation that I will re-visit the issue "when things calm down".
    One of those opaque things is the function, significance, or use of "sequence" in the context of APEX Application Builder and application pages.
    I am working through the Oracle-By-Example application labeled OBE_PROJECTS. I have created the Master-Detail form, but it has not come out as expected. According to the instructions, when I created the page, I designated the home page as its parent. Yet, when I run the application, the icon for the master-detail form does not appear.
    I assume that I've fat fingered something when I built the page and attempt to correct it. I think that the answer will lie in the task "Reparenting page hierarchy". When I look at the "Create/Edit Breadcrumb Entry page", I see in the "Entry" region, that the Parent Entry is, indeed, correct ... that is "Home (Page 1)". On the other hand, the text box labeled "Sequence" is set to "10". And this is the same value as the Home Page itself. Can that be correct? Shouldn't my Master-Detail page have a sequence number subordinate to the Home Page?
    Any help/elucidation will be appreciated.
    Regards,
    Gus

    Varad,
    I hadn't gotten that far yet. I'm still following OBE script and accessing the page from the "Run Page" icon in application builder.
    The issue itself, pages not showing up, is solved for me. I had anticipated that simply declaring the parent of Master-Detail page to be home page would automagically make those objects appear on the home page.
    Slogging through the Oracle By Example, I learn that one must actually edit the home page to have them appear (how barbaric!)
    But, the question of exactly what "page sequence" means and how it's supposed to be used is still there.
    Thanks for the Response,
    Gus

  • Application Builder and Corrupt VIs

    Howdy All,
    I'm developing a Medium-sized application in LabVIEW 7.0 used for instrument control. This application has grown over-time, and currently contains approximately 400 VIs. The basic structure of hte appliation is one main VI that has an instrument status display on the bottom, and a sub-panel on the top, into which all dialogs are loaded for user interaction. Each major task has it's own VI that is loaded into the subpanel as appropriate.
    I've read a few stories on the developer exchange about VIs becoming corrupt. I thought these were freak occurences, because by and large, it appears that LabVIEW is fairly stable. However last week I had a VERY scary experience.
    I was demonstrating to a collegue the properties of an XY graph control. We changed the colour of one of the plots, then hit cancel. LabVIEW complained of an internal error involving undo.cpp and proceeded to crash. I figured the crash was caused by some strange sequence of events, didn't think much of it, and reloaded my application. After making some changes, I went to the Application Builder to build the application. However the application Builder was complaining about a "missing board" in the DEFAULT build file. I knew immediately that something was VERY wrong. (When I say default build script, I'm referring the default script that is loaded when you press the "Build application or shared library..." button in the tools menu).
    (As a side note, does anyone know why the LabVIEW application builder gives such terrible error messages? I always get that "missing board" error when either: one of my support files cannot be found, or one of my dynamic VIs is not executable. Since the error doesn't pinpoint a file, I neeed to go through the files one by one - which is a pain because I have a lot. Another question, why does the application builder ALWAYs ask if you want to save changes to build script, even if you haven't made any changes?)
    After loading my build script for the application (which I've used HUNDREDS of times), I got the "missing board" error. I didn't think there was a problem with any of my paths or VIs, but I went throgh each included support file and dynamic VI in the build script to make sure it was there. Though there seemed to be no problems with any of the files, LabVIEW continued to complain.
    I figured the problem was specific to the computer I was working on, so I copied the source to another development machine to complete the build. I was VERY scared to find that I got the SAME error on the DEFAULT build script! Also, my actual build script refused to load properly.
    This was late at the end of a long day, so I decided to turn of my machines and go home. The next morning, everything worked fine - I was able to build the application, and I haven't had a problem since. (Maybe it was a bad dream, but I have clumps of hair on my desk from the night before...)
    I found this experience to be UTTERLY TERRIFYING. Once I had to revert to an archived copy of one of my main VIs, because the current version refused to open, claiming it was corrupt. Since I don't know what's going on behind the scenes in LabVIEW, I'm afraid that tiny internal LabVIEW errors might be adding up. I back-up the source very regularily, since it is such a large project, however I have *real* way of inspecting the integrity of the source.
    Does anyone know (A) why this might have happened - especially when the problem reproduced itself on multiple machines (B) has anyone had similar experience with internal LabVIEW errors or corrupt source (C) what sort of internal errors might be piling up that might cause a VI to claim it is "corrupt".
    All input is appreciated.
    WG

    Hi Robert,
    For the undo.cpp error, I got a couple different line numbers but didn't write them down. If I get them again, I'll be sure to get the specifics for you.
    As for the "missing board", I also got that description a little wrong - the error I'm talking about is:
    "Error 7 occured at Inovke Node in Dist read linkages.vi->Dist Cmp Settings to Disk Hier.vi->Build Application.vi
    Possible reason(s):
    LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for hte operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Unix.
    NI-488: Non-existent board."
    As you can see, I meant "non-existent board". This error is very easy to reproduce - m
    ake a build script and include some extra files. Save and close the build script. Move or rename some of the extra files included in the build. Reload the script. You should get that not very helpful error.
    Now that I think about it though, maybe that NI-488 error refers to GPIB control, which I think I have installed, but don't have a GPIB card installed... hmmm... no reason that error should be popping up *there* though...
    I could have *sworn* I would also get that error when one of the dynamic VIs in the build is not executable, but I can't seem to reproduce that right now.
    Tying back to the original thread - what makes a VI corrupt? I imagine if you cracked the binary file open yourself and messed around with some bits you would probably make the VI corrupt, but I'm assuming that editing a VI normally (ie through LabVIEW) should NOT cause the VIs to become corrupted. Any information on VIs becoming corrupt? Is it somehow related to the undo.cpp errors?(when trying t
    o undo some last change that wasn't recorded properly, the VI is modified improperly - after you save and close, it won't reopen?)
    Victrick

  • Application builder exe does not load excel

    I have used application property node and invoke node to cerate a set of VIs that read and write data to an Excel sperad sheet.  This works fine in when running in LabVIEW, however when I run myApp.exe as build from application builder, the data does not get logged to Excel.  The file dialog appears to  open the XL Spreadsheet but not data gets logged nor is any error reported?
    What is going on?   All the VI are in the same project folder?  Is there some additional addon run-time the must be installed on the target machine?  I am uisng LabVIEW 2012 on the development station with Win7 Pro and Office 2010 on both the devleopment station and the target system.  Is there one document that describes using Application Builder?   It was not clear that I needed both LabVIEW and VISA run-time engines to get my application.exe to run on the target.  Is there something simialr I must do to get Office to work as well? 

    I was finally able to track this back through by starting from scratch and received an error code, which led me to this post:
    https://forums.ni.com/t5/LabVIEW/Error-2147319779-Excel-ActiveX-and-Broken-LabVIEW-Icon/td-p/2354776
    Deleting the "1.7" items solved the problem.

  • Is it possible to embed DAQmx in Installer(created by Application Builder)?

    The good thing of Installer (created by application Builder) is that it also integrates LabView Runtime Engine along with supports like Serial port support, Port I/O support etc. Due to which one can install the application developed by Labview on any system wheather that contains Labview or not, as the engine required by that application also gets installed.
    But problem with my application is that it uses DAQmx related stuff, so I have to install DAQmx 8.0 prior to running my application installer on any system. Is it possible that the DAQmx related stuff required by my application also gets install through same installer as it installs LabView Runtime Engine, so that the distribution of my application donot require the complete installation of DAQmx.

    You need to use LV 8.0.  You can add NIDAQ to your installer in LV 8.0.  In previous versions I do not think it is possible.
    see: http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1
    Matt
    Matthew Fitzsimons
    Certified LabVIEW Architect
    LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

Maybe you are looking for