Build application labview 8.5 database toolkit

Can someone help me on how to build an application and installer for a vi that uses the database connectivity toolkit in labview 8.5?
I know how to do it in Labview 7.1 and the pdf user manual explains the 7.1 method but I have had no luck in finding anything for 8.5. The problem is that you need to load a build script and I cannot find a way to do this in 8.5....
I know this is not hard at all, I just dont have the information...
Thanks a million in advance.

When you select Tools>>Convert Build Script, a dialog will appear asking you for the .bld file you want to convert. It also will ask you to enter a path to a new LabVIEW project. Once you convert, a LabVIEW project will be opened and will have the Statup VIs added and well as a build specification for the EXE. If you had an installer configured in 7.x, a build specification for it as well. In LabVIEW 8.x, you use build specifications to configure build information. You can then right-click on the build specification and select Build.
Message Edited by gmart on 09-11-2008 06:54 AM
George M
National Instruments

Similar Messages

LabVIEW, MSAcess, and Database Toolkit (Exclusivity Problem)

Hi all,
I have recently developed an application that's used for testing production products and sends the final test data to a MS Acess database via the database connectivity toolkit. We've run into a problem with it though. This program needs to be able to run at all times, its a high flow production line. During production though, we have a large group of engineers that need access to this data. Its set up so that only myself and one other person have write access to the directory containing the database, everyone else can only open it as read only.
The problem I'm running into is that whenever the database is open by one of the two engineers with write access OR any one of the other people just going in to review data as read only - the production tester isn't able to save records their creating in LabVIEW. No warning or notice is given to the user in form of error to indicate the data wasn't stored.
I'd like to get this problem fixed but the last time I tried to use the Username/Password inputs on the connectivity VI I ended up locking up access and we finally resorted to just making a new database. Given the amount of data in there now, you could say I'm a little "gun shy" about randomly fooling with the security settings again without a good idea of how to accomplish fixing this.
Basically I just want for that database to be opened exclusively by labview, and prempt anyone who is logged in (aside from one of us with write access...its a small enough group we are fine with just closing the test program for a few minutes while we make changes)
Any ideas on how to do this?
LV7.1, LV8.5

Hi Dennis,
Our IT guys tend to push SQL also. How much work is it to switch over to the other?
You know I'm not sure if its worth it at this point, at most we only have 1-2 people on the database at once. The test computer is always on which brings that number to 1, and it only happens maybe once a day that someone looks at the database and only to check some values in 1 record - then they close out. Aside from the tester, no one else is in there for more than 1-2 minutes tops maybe once every other day. Its just during that time if the user submits his report in that 1-2 minute window - we don't find out about it until someone needs to view that record.
A worst case scenario though is if someone gets in for their 1-2 minute window and gets a call or gets distracted and forgets its open :-/
I did try some quick research....it looks like one recommendation might be to make a "front end" basically another database with a form linked to the data stored in the tables of the original one. That way anyone viewing doesn't go into the storage database itself. I haven't tested this yet though...one question comes up -if they are in this front end thats linked...I wonder if that is considered a "constant connection" to the storage database and we'd still run into the same problem with the storage one "thinking" its open anyhow...
I dunno this database stuff is a bit loopy imho.
LV7.1, LV8.5

Database toolkit & Oracle 11g, problem with timestamps

I tested my application, based on the Database toolkit, with Access and Oracle XE (10g) databases and all was ok. After moving my database to a Oracle 11g server, i get this error for any query involving a TIMESTAMP WITH TIME ZONE or TIMESTAMP WITH LOCAL TIME ZONE column:
ADO Error: 0x80040E21
Exception occured in Microsoft OLE DB Provider for ODBC Drivers: ODBC driver does not support the requested properties.
The error is raised by the "Execute" invoke node in "DB Tools execute query.vi".
Using Labview 2009 and up to date Oracle ODBC drivers on Windows XP

Hi SnamProgetti,
I don't have any useful information about this error. You can try to read this and this document.
Have a nice day,
Simone S.
Academic Field Engineer - Med Region

Database Toolkit compile problem

We are using the
Database toolkit with Labview 8.2.
If a vi that calls a Database vi is used on
several computers then Labview will ask to save it with the following changes :
VI recompiled and sub vi calls modified.
This happens even if nothing was
changed.
This does not happened
on the computer on which the vi was formerly saved but systematically on all
other computers.
The software configuration
is exactly the same on all computers. The entire Labview directory has been
mass compiled on each of them.
This is very annoying
as we have a lot of database vi’s in our program and all the changes applying
to them hide the real changes to other vi's.
Moreover we are working with an SCM tool
(perforce) which oblige us to have exactly the same vi’s on each machine.
Thank you for your
help.
Nicolas

Hello,
For those following this issue, this was reported to R&D
(#41EBTL3Q) for further investigation. As
it turns out, the problem is that the database toolkit is using strict type
definitions. This would normally not be
significant, except that there is a small problem with LabVIEW recompiling the
typedef when it has already been mass compiled (as is required for the database
toolkit in LabVIEW 8.2).
There is another workaround:
1) Install LabVIEW and the
database toolkit on all your development machines
2) Mass compile the database
toolkit (vi.lib/addons/database) on all the machines
3) Copy the vi.lib database
folder of one of these computers (usually found at: C:\Program Files\National
Instruments\LabVIEW 8.2\vi.lib\addons\database) to a CD (or media of your
choosing)
4) Replace this folder on all of
the other computers with the folder from the CD
5) Use the toolkit as normal
If this doesn't work, you can
also probably check in the toolkit folder to perforce, and just have the users
check it in/out each time, but this situation is a little less than ideal, and
we have not tested it.
This problem will NOT affect the execution of the toolkit
(or LV in
general). Most users will only be inconvenienced
by this problem when using Source Code Control.
Have a great weekend!
Travis M
LabVIEW R&D
National Instruments

Application doesn't work after build (database toolkit and report gen toolkit).

I wrote an application using database toolkit and report gen toolkit to retrieve some data from a database, put into a Word doc, save the Word doc and print it. It works fine when I run the vi, but when I build and run it, it does nothing. I have tried all of the settings in Projec Manager that I think might help but it still won't work right. Labview 8.2.1, XP.
Thanks,
Charlie
Solved!
Go to Solution.

Thanks for the help. I finally abondened the Word append table and used the regular report gen append table and got it to work fine. The error was 214682314. That led me to the thread about column numbers must vbe between 1 and 63, but like I said, my coulumn number is 7 so don't know what is going on. Anyway I got the vi to work and do what I want so I guess now the problem is solved (moot).
Charlie

Building application with database

Hello Labviewers,
I build some labview vis wich are functioning very well as long as I execute them in the labview environment.
But when I use the application builder to build an exe file from it the programm can't access the database anymore.
I use Labview 7 and the Database connectivity toolkit to connect to an Access Database.
the Connection to the database is made by an udl file.
Maybe I'm doing something wrong when I include the udl and the mdb file as a support file during the build process ?!?
Or do I have to include some extra files (like I have to when using the report gen toolkit)
Many thanks for your help
Simon

thank you vicky for your reply,
i followed your hint not including the udl files to my support files but had no success.
Generally I use the procedure described here:http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/fcccbc6b519cec2e86256c95007e8fa9?OpenDocument.
Is this still the right way with lv 7.
I still believe that there is some problem with my paths leading to my database. Meanwhile I've tried relative paths and absolut ones with no success.
There is no error message displayed, but the text fields where I'd like to see the results of my sql querys stay white.
Simon

Database toolkit Included in LabView 12?

I thought i read somewhere but cannot confirm
Does Labview 12 come with the database toolkit?
thanks in advance
-Kurt
Solved!
Go to Solution.

Clarification: the Database Connectivity Toolkit has been included with LabVIEW 2014 Professional Development - it is not included with the Base or Full Development systems. The Database Connectivity Toolkit is an add-on for previous versions of LabVIEW.
Chris H
Applications Engineer
National Instruments

I have a application build in labview 8.5 for Windows XP using NI Visa functions to interact with hardware , how to make is work in Windows 7 32 bit and Win 7 64 bit

I have a application build in Labview 8.5 which wroks fine with Windows XP , this program uses basic read /write functions of NI Visa to communicate with Hardware . This application doesnt work with Windows 7 32 bit/64 and Vista . What changes i need to do to make it work for the said operating system

srinivas wrote:
Sorry for confusion ,
My question is what changes i need to do in code or while making the installer to make the existing program work with other Windows operating system
You need to make sure the machine have the corresponding NI-VISA installed. Check in the NI software pages for the right version.
Also make sure that the com port's can be selected when you first start the application. Eg. if you refer to VISA "COM1" on the XP machine It might be "COM2" on the Win7 machine.
Br,
/Roger

Using SQLplus command in LabView Database toolkit

Hi ,
I would like to ask something but before that this is my set up background
OS : Win 7,
LabVIEW : 2012
I have successfully connected with Oracle database using Labview Database toolkit.
The problem now is since I need to query the data from the database,
it will takes time for the labview to process it (since there is so much data in a specific table),
let say that the table in database is "Serial Number", and the data that I want from that table is "SN123"
if I query the data from that table, the labview will process it in a long time since it will not only give me "SN123" but also other data inside the "Serial Number" table.
(Refer to attachment)
but if in SQLplus, there is a command that can be execute to specifically call the "SN123" data,
For the SQLplus, the steps to retrieve the data is like this:
1. Key in the command to get the ID of the "SN123"
2. Key in the command "SN123" ID to retrieve the data.
I wonder if there is a way to put this command on labview database so it will be faster to retrieve the data.
Attachments:
Database.png ‏84 KB

An instrument driver written in Labview, is not the same as a instrument driver used by say Windows. A Labview instrument driver uses standard Labview functions to send SCPI commands to the instrument. You can learn a lot about the instrument by looking into the Labview instrument driver, and how it sends the commands to the instrument. But having the instrument programming manual at hands is also important.
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

How can I build a LabView application that uses the 2012 runtime, on a development system with LabView 2013 or 2014 installed?

I need to build a LabView application .exe to run with the 2012 Runtime, for legacy support. I currently have LabView 2013 installed on my development system, and have 2014 available. How can I build an application that uses the 2012 runtime on this development system? Do I have to downgrade to 2012? Thank you.

We have existing customers that have installed our application that was originally built with 2012 (provided by a contractor that is no longer available). Due to IT regulations, it is far easier to update these customers by simply replacing the .exe file, than creating an install that their IT department must run.
If I have to downgrade to LabView 2012, where can I get the installation for this?

Cannot build application with labview 7.0

I had built application previously using labview 6.X while some of the V.I. are without block diagrams, but I couldn't do that any more with labview 7.0 as a error will be prompted, why is this happening & are there difference in application builder between labview 7.0 and previous version? Must I load those V.I. without block diagrams dynamically now ?

Unfortunately it is impossible to build application with newer version with VIs without block diagrams, which saved in oldest version.
from ni web site:
"National Instruments does not recommend saving VIs without block diagrams because LabVIEW needs the block diagram to recompile the VI after an upgrade. When you upgrade LabVIEW, you must find a version of the VI that includes its block diagram to recompile it. Such a version did exist before the block diagram was removed because it is impossible to create a new VI without a block diagram."
"Based on that information, it should be clear that once a VI is saved without diagrams:
You cannot open or run the VI on any other version of LabVIEW, older or newer."
More information:
http://digit
al.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/00a6bacda1c01a0786256b60006163e7?OpenDocument
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/28c4cb0cf83e1a1d862566e2007a2a9c?OpenDocument
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/fee732f4b1541b9586256bf0006a78ca?OpenDocument
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/0649a3350de20aa186256d91007b3d61?OpenDocument

Application Build problem Labview 8.5.1

Having a problem creating an Installer with 8.5.1. When being built a menu appears asking for
"NI Labview 8.2.1" distribution. Needs to copy a component installed or updated by the distribution to continue building the installer.
Despite trying all of the Disks I have, First quarter DVD, and all of the second quarter CD's it does not recognise any of them. When the CD's or DVD is inserted it shows a nidist.id file which I select (because it says that's what it requires) but them it gives a message stating that
"You cannot choose this folder name; a file of that name exists"
I have tried this build on 2 different machines and get the same response, anyone got any ideas on this or is it a no brainer in 8.5.1?
One last thing if this lot cannot be got to work, the additional files required are:-
Ni Labview Runtime Engine 8.5.1
NI Measurement & Automation Explorer 4.5
NI PXI Config Support for Windows
NI DAQmx 8.7 (unsure if this is included in MAX?)
NI Visa Runtime 4.4
Does anyone know if I just downloaded these from NI website and installed on the computer that will run the final .EXE file it will work?
Labview Version 8.5
Labview Version 8.6
Labview Version 2013

Hello Jack1,
I have been looking into your posts. There are two immediate actions you could try to help. I have identified that you are having issues with the computer recognizing that you have inserted the CD it has requested. Also, you are having trouble with repeatedly being asked to change back and forth through disks, at every attempt to build the installer. As you may need to try this more than once, it may be helpful to you to create a folder for each CD or DVD, and copy and paste the contents of the individiual disks. This software will be recognized, even if copied on to your hard disk.
When you click 'Build', to begin building your installer with your necessary additional resources, you will be asked to insert the last set of CDs or DVDs you have used. However, at the prompt you can click on the 'Folder' icon and browse the folder where you have saved the individual disk contents. The error you were receiving in your first post, "You cannot choose this folder name; a file of that name exists", implies that you were most like click on the *.id file and selecting ok. I have avoided this on my machine by opening the folder with the disk contents, not selecting any files, and the click the 'Current Folder' button. After you have selected it, ensure that you have ticked the box next to 'Cache components from this distribution.' Whether you use the CD, or folders containing the disk contents, this options creates a local copy of the requested files to a cache directory, therefore no requiring the user to input disks, or point to file locations in the future. If you have a repeated patter of building applications and installers, this will quicked your process, and eventually allow to delete the disk contents you have copied to your hard disk.
The disks from your previous installations are requested primarily because of your selection to include NI-DAQmx as an Additional Resource. As this is the main driver, shared components are recognized by the Application Builder. I, therefore, can recommend that you try building the installer with the above steps on your laptop, which your mentioned is a fresh installation.
When you have had a moment to try this, please post back to see if I can answer any further questions on this topic, or know that it has worked.
Regards,
Message Edited by gt3000 on 11-03-2008 03:26 PM
George T.
Applications Engineering Specialist
National Instruments UK and Ireland

Database toolkit memory leaks

I have memory leaks in my Labview application connecting and inserting data into a MSSQL server using Labview Database Toolkit.
Versions: Labview 7.1, Toolkit 1.0.1.
I have searched the forums and searhed everywhere else...I see there are some issues. (For example List tables vi). Removing the list tables vi helped a lot. But I can still see that I'm loosing memory here and there, now and then.
My question is: Is there any general guidlines to prevent all memory leaks mentioned?
Or possibly, will it all go away if I upgrade the versions. (As I understand I have too update Labview to be able to update the Toolkit?)
Best Regards
/Jesper
Solved!
Go to Solution.

Have you seen this Developer Zone document?
LabVIEW Database Connectivity Toolset 1.0.1 Known Issues
Functions, VIs, and Express VIs - ID 2F7E2352
Memory Leak in the Database Toolset in DB Tools Open Schema VI
The DB Tools Open Schema VI leaks memory which if called continuously eventually causes a LabVIEW crash. This is a sub VI of the DB Tools Insert Data VI.
Workaround—At the highest level, if you are continuously updating values in a table, make sure the table already exists and leave the Create Table input to the DB Tools Insert Data VI set to FALSE.
Other than this, the most important thing is to close all references...
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness

Error when building application with Excel included

Hi All !
I've read several post on problems with Report Generation Toolkit when building applications that uses Excel or Word interactivity.
I've included both _Excel Dynamic VIs.vi and _Word Dynamic VIs.vi in my project and added them to the dynamic vis and support files.
When building I get the error :
The VI is broken. Open the VI in LabVIEW and fix the errors.
C:\Programmer\National Instruments\LabVIEW 8.2\vi.lib\addons\_office\_exclsub.llb\_Excel Dynamic VIs.vi
When opening that VI there is no broken arrow and all the vi's included in this is not broken either.
I've tried mass compiling and so on but so far luck.
Regards Morten Kahr
Regards Kahr
Certified LabVIEW Architect
CIM A/S

If you do a search on this forum you will find this to be a common and vexing problem. I myself had this same exact problem about a year ago, and it took me the better part of a day to track it down. As you will find by reading the various threads on this problem, there seems to be no specific cause for this, and it remains a mystery, and the solutions are no better than chanting voodoo, and probably just as effective.
One thing you can try is to force a recompile of your VI hierarchy. Open you top-level VI. If it's set up to run when opened, stop it. Hold down the Control key and click the run button. This will force a recompile of the application. Sometimes this works, sometimes it doesn't. Like I said, voodoo.
Another thing to look for is to check if you are using any diagram disable structures or case structures with a constant wired, as in trying to use the case structure to comment out code.
Are you using classes and passing by reference? There was a mention of this here.

Database Toolkit with Access 2010

Fellow wireworkers,
I have been using MS Jet to connect with an Access2003 database using the Database Connectivity toolkit for a few years now.
New project, LabVIEW2009, MS Office2010 (32bit) on Windows7 (64-bit).
Database Connectivity toolkit installed, example still uses Labview.mdb example database and MS Jet.
Installed the MS Access Database Engine 2010 Redistributable,
Set the connection string with the UDL file to "“Driver={Microsoft Access Driver (*.mdb, *.accdb)};DBQ=[path]\TestDatabase1.accdb" per instructions on the MS DBE 2010 site,
pressed the Build... button on the DataLink Properties wizard dialog,
Set the Machine Data Source to MS Access Database Type:User pressed OK and got this:
Ideas?

From: http://msdn.microsoft.com/en-us/library/cc280478.aspx
Note
On a 64-bit computer, you must run packages that connect to Microsoft Access data sources in 32-bit mode. Both the Microsoft Jet OLE DB Provider and the OLE DB provider for the Microsoft Office 12.0 Access Database Engine are only available in 32-bit versions.
hmmm... I don't know enough about 64-bit Win7 (running MS Office 2010 32-bit). Will need to dig a bit deeper, but as Dennis suggests, my problem could be with Microsoft not LabVIEW.
...Just tried launching the UDL dialog on my 32-bit Win7 laptop running LabVIEW9.0.1(32-bit) and get the identical error (freeze).
When I launch the UDL dialog on my 32-bit Win7 laptop running LabVIEW10.0(32-bit), the UDL dialog works correctly.
Both attempts are after running LabVIEW "as administrator".
I also noticed the LabVIEW10.0 UDL launcher does not flash the "Create Data Link" helper vi that displays an "Initializing" progress bar.
It still could be a Win7 32/64 bit thing, but LabVIEW10.0 works while LabVIW9.0.1 freezes the UDL dialog...
...and yes... my University lab is managed by IT and they have not yet deployed LabVIEW2010 as the upgrade was received too close to the start of the fall semester.
I'll keep digging, but any suggestions would be greatly appreciated....
-Bill =]

Build application labview 8.5 database toolkit

Similar Messages

Maybe you are looking for