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

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 install

Database toolkit install problem – multi versions
I have 2 versions of LV installed on a W7 box. The Database Connectivity Toolkit runs fine for the 2009 version. The 8.6 version has broken VIs. Error message - expired or invalid licence.
The tool was not installed properly but every time I try to install it the installer tries to overwrite the 2009 version instead of the 8.6 version. When I do a custom install and try and set the correct location, the installer overwrites the location I set and adds a LV2009 directory.
How can I install it to the correct version of LV?

DKA wrote:
How can I install it to the correct version of LV?
By taking the same version of the Toolkit as the version of LabVIEW is where you want to install it.
Christian

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

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

SQL Query Works in MS SQL Server 2008 but not when using Database Toolkit

I have this SQL query:
DECLARE @DataTypeTable TABLE (
Name varchar(128),
TypeID INT)
--Add comma delimeted data type names to temp table
INSERT INTO @DataTypeTable (Name)
SELECT * FROM WhatWeShouldDoRead.func_Split(@DataTypeTrimmed,',')
SELECT Name FROM @DataTypeTable
Which takes a comma delimited string and returns the string as a table. It works correctly in Microsoft SQL Server Management Studio. When I run this as a stored procedure I get back nothing. There are no errors, SQL or otherwise. I've verified that I am connected to the correct database and that the stored procedure is loaded by changing the no error string that is reported from this stored procedure (that code is not shown in the above example). Has anyone seen this problem before, or have any experiance with SQL/Labview interfaces to tell me what I'm doing wrong?
Thanks in advance.
Solved!
Go to Solution.

After doing some more research it appears that the database toolkit cannot interface with any table results from any type of temp table. It may have to do with the fact that MS SQL 2008 stores temp tables in a seperate database (tempdb) and not the database you are currently connected to. See this link for a good artical on temp tables:
http://databases.aspfaq.com/database/should-i-use-a-temp-table-or-a-table-variable.html
If possible, I'd like a someone to prove me wrong, but for now will have to settle for exporting the contents of a temp table through a string.

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)

Selecting data on basis of string from ms access using database toolkit

i want to read data from ms access in labview using database toolkit,but the problem is that i want to enter/select pipetype and other fields must be filled from the database with respect to pipe type intead of indexing(1,2,3,....)..kindly tell me how to make my selectio from database depending on pipe type.
Attachments:
database.zip ‏324 KB

What is pipetype and what exactly do you mean by 'selecting data on basis of string'.

Possible DateTime bug in Database Toolkit

Hi!
I dont have the database toolkit here, and it seems you cannot download a 64-bit evaluation ...
Bug? I've been writing DateTime fields to a database through the proper use of clusters and Inserts, but it seems i never get any fractional seconds. The datetime controls shows them and the database fields should support them (atleast it's showing .000 at the end) so i'm wondering: Does it somehow use regional settings for time so it's using my decimal comma and thus ditching the fractions?
/Yamaeda
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV
Solved!
Go to Solution.

Actually if you do a parametrized insert there is not necessarily any string involved. The datatime value could be directly passed as a DB variant. But I'm not sure what the internal LabVIEW conversion from it's native control datatypes to a variant does.
Another idea might be a mismatch with the used decimal character. Some local settings use decimal comma, others use decimal point. ADO, which is used by the Database Toolkit, has a strong preference to use the local decimal format, and so does LabVIEW, unless you disable that with an INI file setting. But if your server uses a different setting you have a problem!
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Reentrant Execution gets slower.... (DATABASE TOOLKIT)

Hi All
I am LabVIEW 2009. Application is typically running on Windows XP.
I have a sub VI which is inserting data in MS SQL server. This vi is using database toolkit for inserting data into database.
I made this VI reentrant, and my toplevel is dynamically calling its clone.
Now suppose if my top level vi opens 20 clones of sub vi, everything seems to be ok. As per logic all 20 clones are inserting data into database parallely/second. (20 records/second)
Now, if my top level vi opens 100 or 1000 clones of sub vi, sub vi's are not inserting 100 or 1000 records/second into database. It means their executions speed decreased. (approx. 35 records/second).
Are my database VI's are creating this overhead or jitter. My SUB vi is reentrant, but when I diagnosed database toolkit, I found that almost all VI's are not reentrant.
After that, I edited all DATABASE toolkits VI's, I made all VI's reentrant, but still problem is unsolved.

Matthew Williams wrote:
As I understand it, the DB Toolkit .vis work through ActiveX, which itself is not re-entrant and may be a bottleneck.
We are battling the same problem, haven't found a good solution. It looks like we will have to go with two queues, one high
priority, one lower that only accesses the DB on a best effort basis. Not ideal.
From conversations with NI, I believe the LV 2010 DSC add-on is multi-threaded regarding DB access. Don't know whether
the improvements are available through the DB Toolkit, though, and we are stuck on 8.5.1 for this particular project.
Matt
Mike Porter has figured out how to get at DB using ADO and aviods the toolkits completely. He is way beyond me in this area but maybe that is an avenue that could help you.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Database toolkit

Hello!
I want to import to Labview two colums of a MySql database.
One of this columns is a column of double. I use database variant data to data, and I specify that is double with a constant....but it appears an error message that cannot convert the input data in this data type.
Someone knows the better way to read in Labview the information of a database....if is a colum of double.....and if is a column of data/time.
P.Derhaps this block only allows you import one element??In this case how i can import it? An Vi's example would help me a lot.
Thanks!!

Hi Bob,
What specific errors are you getting? Does the problem come when the program is run or right when you open it after saving for the previous version? If you already have the Database Connectivity Toolkit 2009 installed (it sounds like you do) we should check to make sure it is activated. To do this use NI License Manager (Programs>>National Instruments>>NI License Manager). If you have not activated products with NI License Manager in the past, it is discussed here.
If you do have the Database Connectivity Toolkit 2009 installed and activated, try to repair the install. Follow the steps in the How can I Repair my LabVIEW Installation? Knowledge Base, but repair the install of the Database Toolkit not LabVIEW.
The next option would be to completely uninstall and reinstall the toolkit. If installing from the disc doesn't seem to be working, try the online Database Connectivity Toolkit download
I hope that info is helpful!
Matt
Product Owner - NI Community
National Instruments

Re: [iPlanet-JATO] sp3 jsp compiler problem

Weiguo,
First, Matt is correct, the regular expression tool is perfect for general text
substitution situations, and as a completely independent tool its use is not
restricted to migration situations (or file types for that matter).
Second, I sympathize with the unfortunate trouble you are experiencing due to
Jasper's (perhaps more strict) compilation, but in what way did the iMT
automated translation contribute to these inconsistencies that you cited?
1. Changed the case of the tag attribute to be the same as what's
defined in tld.
example: changed OnClick to onClick
The iMT does not generate any OnClick or onClick clauses per se. In a
translation situation, the only way "OnClick" would have been introduced was if
it had been part of the pre-existing project's "extraHTML" (which was written
by the original customer and just passed through unchanged by the iMT) or if it
was added manually by the post-migration developer.
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be
similar to the OnClick situation described above?
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
Again, the content tag would never have been generated by the iMT. There was no
equivalent in the NetDynamics world, so any content tags in your code must have
been introduced by your developers manually. Its a shame that jasper is so
particular, but the iMT could not help you out here even if we wanted to. The
constants that are used by the iMT are defined in
com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can see, the
only situation of a closing tag with any space in it is
public static final String CLOSE_EMPTY_ELEMENT = " />";
But that should not cause the type of problem you are referring to.
Mike
----- Original Message -----
From: Matthew Stevens
Sent: Thursday, September 06, 2001 10:16 AM
Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
Weiguo,
Others will chime in for sure...I would highly recommend the Regex Tool from
the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
posted to the group (even recently) on directions and advantages of creating
your own RULES (rules file) in XML for arbitary batch processing of source.
matt
-----Original Message-----
From: weiguo.wang@b...
[mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174144234026000079108238073194105057099246073154180137239239223019162">weiguo.wang@b...</a>]
Sent: Thursday, September 06, 2001 12:25 PM
Subject: [iPlanet-JATO] sp3 jsp compiler problem
Matt/Mike/Todd,
We are trying to migrate to sp3 right now, but have had a lot of
issues with the new jasper compiler.
The following workaround has been employed to solve the issues:
1. Changed the case of the tag attribute to be the same as what's
defined in tld.
example: changed OnClick to onClick
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
As I see it, we have two options to go about solving this problem:
1. Write a script which will iterate through all the jsp files and
call jspc on them. Fix the errors manually when jspc fails. Jspc will
flag the line number where an error occurs.
2. Write a utility which scans the jsp files and fix the errors when
they are encountered. We should define what's an error and how to
correct it. It's best if we combine this with solution 1 since we
might miss an error condition.
Actually, there might be another option, which is seeking help from
you guys since you have better understanding of JATO and iAS. Can you
do anything to help us?
We would be happy to hear your thoughts.
At last, I would like to suggest modifying the moko tool so that
these rules are enforced and the generated JSPs work with the new
compiler. This is for the benefit of any new migration projects.
Thanks a lot.
Weiguo
[email protected]
Choose from 1000s of job listings!
[email protected]
[Non-text portions of this message have been removed]

Thanks a lot Matt and Mike for your prompt replies.
I agree completely that iMT doesn't introduce the inconsistencies.
About the three cases I mentioned, the third one happens only in
manually created JSPs. So it has nothing to do with iMT. The first
two are mainly due to the existing HTML code, as you rightly pointed
out.
The reason I made the suggestion is since we know that case 1 and 2
won't pass the japser compiler in sp3, we have to do something about
it. The best place to do this, in my mind, is iMT. Of course, there
might be some twists that make it impossible or difficult to do this
kind of case manipulation or attribute discard.
Weiguo
--- In iPlanet-JATO@y..., "Mike Frisino" <Michael.Frisino@S...> wrote:
Weiguo,
First, Matt is correct, the regular expression tool is perfect for general text substitution situations, and as a completely independent
tool its use is not restricted to migration situations (or file types
for that matter).
>
Second, I sympathize with the unfortunate trouble you are experiencing due to Jasper's (perhaps more strict) compilation, but
in what way did the iMT automated translation contribute to these
inconsistencies that you cited?
>
1. Changed the case of the tag attribute to be the same as what's
defined in tld.
example: changed OnClick to onClick
The iMT does not generate any OnClick or onClick clauses per se. In a translation situation, the only way "OnClick" would have been
introduced was if it had been part of the pre-existing
project's "extraHTML" (which was written by the original customer and
just passed through unchanged by the iMT) or if it was added manually
by the post-migration developer.
>
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be similar to the OnClick situation described above?
>
>
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
Again, the content tag would never have been generated by the iMT. There was no equivalent in the NetDynamics world, so any content tags
in your code must have been introduced by your developers manually.
Its a shame that jasper is so particular, but the iMT could not help
you out here even if we wanted to. The constants that are used by the
iMT are defined in
com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can
see, the only situation of a closing tag with any space in it is
public static final String CLOSE_EMPTY_ELEMENT = " />";
But that should not cause the type of problem you are referring to.
Mike
----- Original Message -----
From: Matthew Stevens
Sent: Thursday, September 06, 2001 10:16 AM
Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
Weiguo,
Others will chime in for sure...I would highly recommend the Regex Tool from
the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
posted to the group (even recently) on directions and advantages of creating
your own RULES (rules file) in XML for arbitary batch processing of source.
>
matt
-----Original Message-----
From: weiguo.wang@b...
[mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174048139046">weiguo.wang@b...</a>]
Sent: Thursday, September 06, 2001 12:25 PM
Subject: [iPlanet-JATO] sp3 jsp compiler problem
Matt/Mike/Todd,
We are trying to migrate to sp3 right now, but have had a lot of
issues with the new jasper compiler.
The following workaround has been employed to solve the issues:
1. Changed the case of the tag attribute to be the same as
what's
defined in tld.
example: changed OnClick to onClick
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
As I see it, we have two options to go about solving this problem:
>>
1. Write a script which will iterate through all the jsp files and
call jspc on them. Fix the errors manually when jspc fails. Jspc will
flag the line number where an error occurs.
2. Write a utility which scans the jsp files and fix the errors when
they are encountered. We should define what's an error and how to
correct it. It's best if we combine this with solution 1 since we
might miss an error condition.
Actually, there might be another option, which is seeking help from
you guys since you have better understanding of JATO and iAS. Can you
do anything to help us?
We would be happy to hear your thoughts.
At last, I would like to suggest modifying the moko tool so that
these rules are enforced and the generated JSPs work with the new
compiler. This is for the benefit of any new migration projects.
Thanks a lot.
Weiguo
[email protected]
Choose from 1000s of job listings!
[email protected]
Service.
>
>
>
[Non-text portions of this message have been removed]

How can I delete a row in access using the database toolkit?

I want to delete just one row of a access table using the database toolkit. Can it be done and if so How?

Take a look at page A-1 of the database connetivity manual. It has information on making a sql query that will delete. You will need to use this command with the dbtools execute query function. Look in the shipping examples for an example with this function.

Servlet Compilation Problem !

Hi,
I am just starting to learn servlets and I got problem in compiling them. I got compilation error in
import javax.servlet.*;statement. Seems that the compiler cannot find the servlet package. I got J2EE 1.4 beta installed on my machine but there is no servlet.jar package. I am using J2SDK 1.4.1_02, J2EE 1.4 beta and Tomcat 4.1.24.
Can anyone help me with my servlet compilation problem?
Thanks in advance!
Josh

servlet.jar is here :
<tomcatdir>\common\lib
add it to your compiler classpath

Compilation problem in a JSP page

Hi all,
I'm trying to write a jsp page and some java stuff in it.
It goes something like this -
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<%@ page contentType="text/html;charset=windows-1255"%>
<html>
<head>
    <meta http-equiv="Content-Type" content="text/html; charset=windows-1255"/>
    <title>Michael</title>
</head>
<body>
<%
          String strError="";
%>
</body>Now the problem is that I get compilation problem about the use in java -
"String cannot be resolved to a type"
I know for sure that in other computers it's work, the question is what I'm missing?
I have Java VM installed and I've downloaded and installed the latest JDK, what else?
thanks,
Michael.

Michael4488 wrote:
BalusC wrote:
Then you should be using JSTL/EL.I don't familiar with this technology, any way - Its work on one computer so in my understanding it should work on the other as well.It is not related to the actual problem. It was just a comment on your code. Using scriptlets is considered as bad practice.
I understand that of course, but I don't use any configuration file or set any special parameters in my computer.
What exactly does the compiler need in order to recognize the Java code in the JSP page? If i manually add the JAVA_HOME environment variable it will work?
where should I refer it to? "..\Java\jre1.6.0_07\lib" will do?It must point to the root installation directory of the JDK (thus not the JRE!).

Database Toolkit compile problem

Similar Messages

Maybe you are looking for