Inifile created by the application builder

Why is an almost empty ini file (with the same name as the executable)
always created in the installation folder when installing a labview
program created with the application builder?
I want to distrubute my own inifile with the installer but it seams
that it is overwritten. I have one other file copied into the
installation folder by the installer and it is installed just fine. Any
suggestions? Do I have to change my inifile name (don´t want that)?
/ Roine

Hello!
Here you have some more information that you might find helpful when it comes to *.ini files and executables created in LabVIEW:
Setting LabVIEW Preferences For a Windows Executable
http://digital.ni.com/public.nsf/websearch/65f76f247012df68862562c70073be06?OpenDocument
How Do I Prevent Automatic Creation of an INI File in Windows Start Directory when I Run a LabVIEW Executable from the Same Directory?
http://digital.ni.com/public.nsf/websearch/40E442486D81582E86256D16004D5D07?OpenDocument
Will My Application's .ini File Be Overwritten When I Run My LabVIEW Stand Alone Executable?
http://digital.ni.com/public.nsf/websearch/680ADAAD4A2E97F586256DC80074B471?OpenDocument
Regards,
Jimmie A.
Applications Engineer, National Instruments
Regards,
Jimmie Adolph
Systems Engineer Manager, National Instruments Northern Region
Bring Me The Horizon - Sempiternal

Similar Messages

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.

What are the options in the application builder application.ini file

What are the options that I can add in the application.ini file that is created by the application builder.

They are about the same as LabVIEW.ini. Scott Hannahs has a list of ini settings for several versions of LabVIEW that can be found here.

Can I call a regular LabVIEW VI from my C# application without first creating a DLL in the application builder?

I am writing a C# application and have LabVIEW 8.2 and the Application Builder. I want the application to call different standard VIs included in LabVIEW. One way to solve this is to create a blank VI, insert the desired standard VI, have the Application Builder create a DLL and then let the application call the DLL. Something tells me there must be a shortcut to this, is there? Aren't all standard LabVIEW VIs really DLLs underneath the surface? Can I somehow call those DLLs directly?

arnold_w wrote:
Aren't all standard LabVIEW VIs really DLLs underneath the surface?
NO, LabVIEW is a programming language and contains a lot of primitives. Some VIs are wrappers for DLL's but even calling these from C(#) might be a problem.
You can exploit the LabVIEW ActiveX interface to perform all the actions you want.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

The executible I build with the application builder does not function the same as my VI file.

I am using a USB 6008 device with the newest DAQmx drivers and Labview
8.2 to make analog voltage readings. Within my main VI I first
create a data folder in the same location as the VI using a property
node and then use case statements to call two sub VIs that create a
data file within the data folder and then collects data. When I use the
application builder to create an executible the resulting file does not
operate the same as the origional VI. The program appears to be
reacting to button presses on the GUI, but there is no indication that
the data folder is being created or that any measurements are buing
made. Are there any known issues that may account for this
anomily?
-Mike
Message Edited by TMBurleson on 10-16-2006 03:09 PM

Are you using the VI Path property, using a reference to the current VI?
I could be wrong, but if you're attempting to use a path relative to the current VI, I think that does indeed change in a built application. If your VI used to be C:\somewhere\foo.VI, then after building its path would actually be C:\somewhere\foo.EXE\foo.vi . Thus, if foo.VI used to try to make a folder like C:\somewhere\datafolder, the built application would be trying to make C:\somewhere\foo.EXE\datafolder , which wouldn't work.
This is sort of a shot in the dark, but does this sound like it might be the case?
EDIT: Dennis beat me to it.Message Edited by kehander on 10-16-2006 03:26 PM

Use of the button in the application builder

I'm trying to use the application builder of oracle 10g express, i have three list objects and a button, when i click on the button i want to create a new record in the database with the data in the list objects. I have seen that there's an option in the button ("database actions") that let me choose an action (INSERT/UPDATE/CANCEL) but i haven't found where i can put the code for the insertion.
Someone could help me?
thanks

Adithya,
When Delete is clicked..
Only when you run again the same application, you will see that the personalization get deleted
I think you can use RESET to resets the view without running the application again.
RESET will show you the view without any personalization effects.
Thanks
Ramakrishna

What is the logic in the Application Builder

Hi guys,
What is the logic in the application builder when creating e.g a Report. When we create a static report we go through these four steps:
<ul>
Display Attributes
Source
Report Attributes
Conditional Display </ul>
Starting from the "Source" step we can Click "Create Report", and create the report .....
is there a table for each step... or there is a collection for each step. So, when we click Create Button the collections are inserted into tables, then get emptied. ?????
In my case, i have three real-estate entities: landlords, properties, and marketing. it goes like this:
enter the landlord details, then click create to move to the next page to enter the property details, then click create to move to the next page to enter the marketing details.
i hope that my question is clear..
Best Regards,
Fateh

Fateh wrote:
Hi guys,
What is the logic in the application builder when creating e.g a Report. When we create a static report we go through these four steps:
<ul>
Display Attributes
Source
Report Attributes
Conditional Display </ul>
Starting from the "Source" step we can Click "Create Report", and create the report .....
is there a table for each step... or there is a collection for each step. So, when we click Create Button the collections are inserted into tables, then get emptied. ?????
In my case, i have three real-estate entities: landlords, properties, and marketing. it goes like this:
enter the landlord details, then click create to move to the next page to enter the property details, then click create to move to the next page to enter the marketing details.That would be called a "wizard" in APEX (as frequently used in the Application Builder as you say). There's a "Wizard wizard" as an option when creating a new page that enables you create and link the basic multiple page structure. Themes have "Wizard Progress List" (vertical orientation) and "Wizard Progress List, Horizontal Train" (horizontal) list templates that can be used as stage progress indicators. You have to construct the contents of each page using standard components. Once the "Wizard wizard" is completed there's nothing to indicate that the pages are logically related—strangely it doesn't even generate a wizard progress list for you.
Use Collections to store the data from intermediate stages before final processing if all of the data is captured in one session. If you want persistence across sessions (e.g. allowing users to enter information over several days) use separate drafting/staging tables instead of/in addition to collections to capture the data before final validation and promotion to the main tables.

Full windowsize with the application builder

Hi,
I creat an executable file with the application builder. The problem is, the window is not as large as when I starte the program in Labview. Now the Frontpanel is cut on the bottom. What is the problem ?
thanks for help
stevi

Hello Stevi,
You should probably check your VI Properties for window size. First, make sure your front panel is sized exactly how you want it to appear. Then go to File >> VI Properties, and select Window Size from the drop-down box. Click on the "Set to Current Window Size" button. Also select "Maintain Proportions of Window for different monitor resolutions". These two selections should ensure that the VI and/or EXE will run with the desired window settings.
Hope this helps!
Liz Fausak
National Instruments

Cwgraph3d and the application builder

Hi folks
I'm workings with LV 7.1 and i did an apllication using the cwgraph3d.   I'm trying to create an executable/installer with
the application builder but it doesn't work at all in the host pc. The graphic doesn't appear.
How can i fix this?
              Thanks to all.

This is often a problem, often discussed on this forum. One step should be to study the LabVIEW Advanced Application Builder tutorial.
Chilly Charly    (aka CC)
         E-List Master - Kudos glutton - Press the yellow button on the left...

Report Generation for Excel does not work after using the Application Builder

I have a VI that writes data to an Excel file using the Report Generation Toolkit. I recently compiled the VI into a single Application (EXE) using the Application Builder. My VI runs its tests properly, but no data is written to Excel. What could be the cause? I don't receive any error messages.

Hi
I usually build exe-files, which sometimes also have report functionality.
Open the Application Builder and check the following things:
1. Add the following vis: _Word Dynamic VIs.vi, _Excel Dynamic VIs.vi They should be located in the directory ..\LabVIEW X.X\vi.lib\addons\_office in the llbs _wordsub.llb and _exclsub.llb (report1.jpg)
2. If you use an Installer, go to the Advanced Settings. There you can select some things to include in the Installer. Check if "NI Reports Support" is selected. (report2.jpg)
These are the things I always do, if I need reports and I never had problems up to now. I made two screen-shots of these settings.
Hope this helps.
Thomas
Using LV8.0
Don't be afraid to rate a good answer...
Attachments:
report.zip ‏25 KB

How can I use a shared library made with the application builder?

Hi,
I am using LabVIEW 7.1 running on Slackware 10.1 (kernel 2.4.29) and I am trying to call a graph display from a C program that I use for debugging VME access from a VMIVME controler. So using the application builder I built the VI as a shared library (graph.vi -> graph.so) containing a function called "graph". In my main program the call to the dlopen fails with the error: "graph.so: undefined symbol: UninitLVClient". When I examin graph.so with nm I see that UninitLVClient and other LabVIEW functions are indeed undefined and using ldd shows that graph.so has dependencies only on libc.so.* and *linux*.so.* but not on LabVIEW related stuff. Those functions are defined in the liblv.so that's in the cintools directory but I have no idea if the user is supposed to use that.
So I think I am missing an important concept here. Can somebody help or direct me to some documentation (I found lots of information about how to link external code to LabVIEW but nothing about how to link LabVIEW code to an external program)?

Thanks Watermann,
your message has been very useful so now I am linking to the proper library but I still have problems when trying to load dynamically the shared library produced with LabVIEW. It is strange that I could successfully load the lvrt library at loading time but it does not work when I am loading the library at execution time.
I made a small LabVIEW program that prints a hello window and I am calling it from a C program. In the first program main.c I am linking to the lvrt library at loading time and it works but in the second one I am linking dynamically at execution time and it does not work. For my work I need to be able to load code done in LabVIEW at execution time. Any help is appreciated!
Program main.c:
// small program to call a LabVIEW shared library
#include
#include
#include "hello.h" // got this from the LabVIEW builder, i.e. when I made the hello.so
int main(void)
printf("Hello from C!\nLets call LabVIEW now\n");
hello();
printf("Bye ... \n");
return 0;
The command to compile main.c, i.e. linking shared library lvrt when loading main program:
gcc -Wall -I /usr/local/lv71/cintools/ -o main main.c hello.so -l lvrt
The LD_LIBRARY_PATH has been defined and exported:
$ LD_LIBRARY_PATH=$PWD
$ export LD_LIBRARY_PATH
IT WORKS!
Program main2.c:
// small program to call a LabVIEW shared library
#include
#include
#include
int main(void)
void * h_lvrt;
void * h_hello;
void (* hello)(void);
char * error;
printf("Hello from C!\nLets call LabVIEW now\n");
// open LabVIEW RunTime shared library
// in my computer located at /usr/local/lib/liblvrt.so
h_lvrt = dlopen("/usr/local/lib/liblvrt.so", RTLD_NOW);
// check for error
error = dlerror();
if (error) {
printf("error : could not open LabVIEW RunTime library\n");
printf("%s\n", error);
return 1;
// open hello shared library
// in my computer located at /home/darss/lv_call/hello.so
h_hello = dlopen("hello.so", RTLD_NOW);
// check for error
error = dlerror();
if (error) {
// close LabVIEW RunTime shared library
dlclose(h_lvrt);
printf("error : could not open hello library\n");
printf("%s\n", error);
return 1;
// get function hello from library hello.so
hello = dlsym(h_hello, "hello");
// check for error
error = dlerror();
if (error) {
// close hello shared library
dlclose(h_hello);
// close LabVIEW RunTime shared library
dlclose(h_lvrt);
printf("error : could not get the hello function\n");
printf("%s\n", error);
return 1;
// call hello function
hello();
// close hello shared library
dlclose(h_hello);
// close LabVIEW RunTime shared library
dlclose(h_lvrt);
printf("Bye ... \n");
return 0;
The command to compile main2.c, i.e. dynamically linking library lvrt at execution of main2 program:
gcc -Wall -o main2 main2.c -l dl
The LD_LIBRARY_PATH still defined and exported.
IT DOES NOT WORK!
Program output:
Hello from C!
Lets call LabVIEW now
error : could not open hello library
/home/darss/lv_call/hello.so: undefined symbol: WaitLVDLLReady

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

Where is the Application Builder Icon?

I just installed Express, logged into the DB home page as SYSTEM, and only saw these icons:
Administration
Object Browser
SQL
Utilities
Where is it?

user463359,
You only get to use the application builder while logged in as a user other than SYSTEM. Try clicking on the Getting Started button on the home page. Follow the directions to unlock the HR schema to get an idea.
Sergio

Using the LabVIEW (PDS), version 6.0, I cannot find the "Application Builder".

Hello,
I use the LabVIEW Professional Development System, version 6.0. However, I cannot find the "Application Builder" in the "Tools" menu.
How can I install this toolkit from the CD?
Thanks.

Hmmm... The App Builder is located in the project folder:
project\prodisttool.llb\build application.vi
Make sure this LLB is in your project folder. Also... have you changed the location of your "Library folder" under tools>options ? LabVIEW looks for the project folder inside your "Library folder" whose default is usually something like this on a PC:
C:\Program Files\National Instruments\LabVIEW\
So the App Builder should be at:
C:\Program Files\National Instruments\LabVIEW\project\prodisttool.llb\build application.vi
If you changed your Library Folder, LabVIEW might not be able to find it, and then you won't see it under Tools

Inifile created by the application builder

Similar Messages

Maybe you are looking for