SQL Toolkit sur Windows x64

Bonjour,
Nous avons acquis la mise à jour LabWindows/CVI 2010 récemment, devons-nous aussi mettre à jour la version de l'instrument SQL en notre possession pour pouvoir accéder à des Bases de Données installées sur des machines Windows 64 bits ou 32 bits et depuis des machines qui elles aussi peuvent être sous Windows 32 bits ou 64 bits ?
Notre version se nomme "SQL Toolkit v2.05" et le fichier "cvi_db.fp" est daté du 21/12/1999.
Merci de vos conseils,
Franck

Unfortunately, I don't speak French so I hope you can understand this reply. The latest version of the SQL toolkit is version 2.2 which was released last year and is available here: http://sine.ni.com/nips/cds/view/p/lang/en/nid/11128
It includes support for x86 and x64 although you ought to be aware that not all database providers offer x64 drivers for their databases. That's not anything CVI has control over though. As new x64 drivers are released, they should work with the SQL toolkit.
Kevin B.
National Instruments

Similar Messages

Why do I get a class conflict between the Prepare SQL.vi and the Get Column Name.vi with the SQL Toolkit compatibility vis from the Database Connectivity Toolkit?

I have done extensive programming with the SQL Toolkit with LabVIEW versions through 6.1. My customer now wants to upgrade to Windows 7, so I am trying to upgrade to LabVIEW 2009 (my latest purchased version) using the Database Connectivity Toolkit, and the SQL Toolkit Compatibility vis. Everything seemed to be going okay with the higher level SQL operations, but I ran into trouble with the Get Column Name.vi.
The pictures below show the problem. The original SQL Toolkit connected the Prepare SQL.vi with the Get Column Name.vi with a cluster of two references, one for connection, and one for sql. The new compatibility vis have a class conflict in the wire because the Prepare SQL.vi contains a cluster with connection, and command references, but the Get Column Name.vi expects a cluster with connection and recordset references.
How do I resolve this conflict?
Thank You.
Dan

I've never worked with the old version of the toolkit, so I don't know how it did things, but looking inside the SQL prep VI, it only generates a command, and the the column name VI wants a recordset. I'm not super familiar with all the internals of ADO, but my understanding is that is standard - you only have the columns after you execute the command and get the recordset back. What you can apparently do here is insert the Execute Prepared SQL VI in the middle and that will return what you need.
I'm not sure why it worked before. Maybe the execute was hidden inside the prep VI or maybe you can get the column names out of the command object before execution. In general, I would recommend considering switching to the newer VIs.
Try to take over the world!

Help, Cannot connect to ODBC database using SQL Toolkit!

Hello All,
I am toying around with the SQL Toolkit evaluation (2.2 + the patch) and I am having difficulty.
I ran the example program "connect" and it seems to work fine.
However, I try to write my own program and I keep getting the same message:
"Function DBConnect: (return value == -10 [0xFFFFFFF6]).
Native error code - 2147467259 0x80004005
The message differs from time to time, but the return value is constant.
I am using both Microsoft SQL Server 2012 and MySQL.
For MySQL I have installed the latest ODBC connector, 5.3.4. Inside the Control Panel/Data Sources(ODBC), I have a DSN named test_mysql in both User DSN and System DSN.
I ran a test on the connection and the test passes. I am not sure if I should use the ansi or unicode driver, I have tried both with the same success.
I am not sure I had configured the SQL Server connection properly, and will attempt that again.
My CVI Code is simple enough:
hdbc = DBConnect ("DSN=test_mysql");
Every time I get a -10 from DBConnect. Either I have something configured wrong or I am missing something.
Does anyone have any suggestions?
Veni Vidi Duci
Solved!
Go to Solution.

Update 2:
After getting off the phone with Tech Support the problem has been identified!
LabWindows SQL toolkit requires 32 bit DNS. My PC is a 64 bit, so my DNS manager defaulted to 64 bit.
I needed to use the 32 bit DNS manager when working with the toolkit.
Once I created my DNS connections using the 32-bit version of the ODBC Datga Source manager, everything worked fine.
See this tech note:
http://digital.ni.com/public.nsf/allkb/E7984C0DA0F0E65086257694005B4CB7
Veni Vidi Duci

How to compact and repair a MS Access database with NI CVI 8.5 (and SQL Toolkit)

Hello
I'm using the SQL Toolkit with CVI 8.5 for accessing MS Access Databases.
Is there a possibility to compact and repair the .mdb file with CVI?
Thanks in advance.

Hello Ulrich,
with compact and repair I mean the MSAccess function "Compact and Repair".
Please follow the link below for more details:
http://office.microsoft.com/en-us/access-help/compact-and-repair-an-access-file-HP005187449.aspx
Normally you can execute this function directly in Access or with the Windows ODBC Data Sources Administrator => "Control Panel" => "Administrative Tools" => "Data Sources (ODBC)"...
I want to execute this function via cvi code and not by hand ;-).
Thank you for your support.
Frank

LabWindows CVI and SQL Toolkit cursor/schema error

We are using CVI 8.5 and SQL Toolkit 2.0.6 to write data to a SQL Server 2008 database. We are utilizing the Microsoft ODBC SQL Server (non-native) driver. We build a transaction that calls stored procedures on the database to write the data. Occasionally we get the following error:
"Could not complete cursor operation because the table schema changed after the cursor was declared"
The error is unusual since we only use one cursor and it is in a stored procedure that gets called by other software hundreds of times a day and never fails. Our database is also designed to only append records, not change existing ones. We're trying to pinpoint the error and I'm wondering if anyone knows if the SQL Toolkit uses cursors to build transactions or if this error has been seen by others. Since upgrading the toolkit or drivers takes a lot of effort, I want to make sure that I understand the problem before I start throwing darts at it. Thanks in advance for any insight.

I've attached the function that's failing. Unfortunately, the code isn't designed with much resolution as to what SQL toolkit call failed, since these calls haven't failed once validated and put into the production environment. Can you tell if any of these functions use a cursor. I could certainly try adding more resolution to the error handling, but since we've only seen errors occasionally in the production environment, I'd need to release a temp version and monitor it. Let me know what you think. Thanks.
Attachments:
StoreTestData.txt ‏5 KB

Need a guideline to install the appropriate version of SQL Server on Windows 8

Hi Everybody, I just started to learn database programming with C#, but i am facing problems over problems. Actually I'm running Windows 8 Pro, x64 Architecture. I tried installing SQL Server 2008 Express and SQL Server Management Studio Express, it do
get installed but was not working when i linked it to c# code. Anybody please guide me about how to install SQL Server and make it running on Windows 8 Pro... Thanks in anticipation
Regards,
Yasir Lateef

Hi Yasir,
Firstly, besides Saeid’s post, you can also install
SQL Server 2008 SP3 Express ,
SQL Server 2008 R2 SP2 Express or
SQL Server 2012 Express on Windows 8. For more details, please review this article:
How to use SQL Server in Windows and Windows Server environments.
Secondly, about how to install SQL Server on Windows 8, you can follow the steps in this similar blog:
How to Install SQL Server 2012 on Windows 8.1.
Thirdly, from your description, SQL Server 2008 doesn’t work on your system, please help to post more details for analysis. We need to know that if you can successfully connect to SQL Server 2008 using SQL Server Management Studio and the error message you
get.
In addition, if you connect to remote SQL Server Express, please complete these steps described in this similar
blog to configure SQL Server Express to allow remote connections.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Oracle Express Database - Windows x64

At the risk of being seriously repetitive, I'll post a question I have seen in various forms for approximately 3.5 years. The user community needs to have a specific, fact-based answer to the problem of no x64 support on Windows. In several threads one can find via Google, people purporting to be Oracle representatives claim a supported version will be available "soon". Soon in my neck of the woods generally means a time frame less than 3 years, but what do I know. Can someone please, please provide a definitive statement of direction on this issue, and assuming this is coming "soon", it would be overwhelmingly wonderful to have a specific date. My company plans/desires/hopes to release software that would embed an Oracle Express db, and frankly I'm about to throw in the towel if I can't get some visibility to this question. As I've heard from many ex customers, "there's always Sql Server".
Regards, Roger Carter, President, DBConnect Solutions, Inc.

Thanks for the update. I followed up with Oracle internally via our Oracle Partnership channel, and they checked with the VP of development responsible for XE. The official response is "there is no date where this will be provided for Windows x64. It is, however, under consideration." In my 25+ years of working with Oracle, I will give you my translation - it is not going to happen anytime soon, and to your point, it will probably be version 12 before you see anything. For us, this is a huge disappointment, and it means we will be abandoning many thing with Oracle. It's my view that they don't care about this vertical one bit.

Installation XE 11. on Windows x64 ( 64-bit) 2008

Dear All ,
I want to know if latest XE edition is certified on Microsoft Windows x64 (64-bit) 2008 OS ?
We have installed specific version on Windows x64 (64-bit) 2008 OS.
We get the following error :
OER 7451 in Load Indicator : Error Code = OSD-04500: illegal option specified
O/S-Error: (OS 1) Incorrect function. !
and there is a respective Doc ID :
Note 1060806.1: OER 7451 in Load Indicator : Error Code = OSD-04500: illegal option specified
Action Plan
========
1. Install 64-bit version of Oracle database software.
2. Upgrade the database from 32-bit version to 64-bit version.
Can we use Oracle XE on specific OS ?

Hello,
I want to know if latest XE edition is certified on Microsoft Windows x64 (64-bit) 2008 OS ?No. See [url http://docs.oracle.com/cd/E17781_01/install.112/e18803/toc.htm#BABHICJH]XE's System Requirements for details.
Similar error messages have been reported here before, e. g. in {message:id=10665775}.
It seems possible to get XE started on 64bit Windows, but it might be a hard fight, especially on a server OS with other possible traps..
Can we use Oracle XE on specific OS ?Sure, all certified 32bit Windows versions or 64bit Linux versions would be fine. See {thread:id=2278170} to get a full report.
-Udo

Support for Windows x64?

I'd like to run Oracle SQL Developer under the 64-bit version of Windows Vista, using the 64-bit Java JDK. Unfortunately, it seems that sqldeveloper.exe is 32-bit only.
I found a Wiki page and another forum thread directly related to this:
- [http://wiki.oracle.com/page/SQL+Developer+FAQ|http://wiki.oracle.com/page/SQL+Developer+FAQ]
- SQL Developer on Windows 2003 x64 Edition "failed to initialize..."
Both mention running sqldeveloper.bat instead of the .exe. However, I see no such .bat file in the release, at least not under the latest 1.5.1.
My only work-around for the moment is to also install and use the 32-bit version of the Java JDK.
Any ideas? Thanks!

Those are both a bit out of date. The 1.5 exe will happily startup up in XP x64, but it flatly refuses to recognise a 64bit JDK. I posted about it here some time ago but got no meaningful response from anyone on the development team. Using a 32-bit JDK seems to be the only available option.

Error export from my database sql 2005 with Windows 2003 abap+java

Hi all
I'm trying to create an Export from my database sql 2005 with Windows 2003, but SAPINST starts with an error. ABAP+JAVA stack
While running the export preparation, I am getting the following error;
INFO 2010-09-08 12:12:43
Output of C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath D:\usr\sap\BID\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jce.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jsse.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_smime.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_ssl.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/w3c_http.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/antlr.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/exception.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/jddi.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/logging.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/offlineconfiguration.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/opensqlsta.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SDMutil.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SLUtil.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\base.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\util.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\sqlserver.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\spy.jar -export -type=keydb "-expfile=C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/usages_data.xml" -log=UTL_load_usages.log -sid=BID -dsn=jdbc/pool/BID -ssprops=D:/usr/sap/BID/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/BID/SYS/global/security/data/SecStore.key is written to the logfile C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/UTL.java.log.
WARNING 2010-09-08 12:12:46
Execution of the command "C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath D:\usr\sap\BID\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jce.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jsse.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_smime.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_ssl.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/w3c_http.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/antlr.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/exception.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/jddi.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/logging.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/offlineconfiguration.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/opensqlsta.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SDMutil.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SLUtil.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\base.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\util.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\sqlserver.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\spy.jar -export -type=keydb "-expfile=C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/usages_data.xml" -log=UTL_load_usages.log -sid=BID -dsn=jdbc/pool/BID -ssprops=D:/usr/sap/BID/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/BID/SYS/global/security/data/SecStore.key" finished with return code 64. Output:
java version "1.4.2_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_13-b06, mixed mode)
ERROR 2010-09-08 12:12:46
CJS-30071 Execution of UTL tool 'C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath D:\usr\sap\BID\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jce.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jsse.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_smime.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_ssl.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/w3c_http.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/antlr.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/exception.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/jddi.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/logging.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/offlineconfiguration.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/opensqlsta.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SDMutil.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SLUtil.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\base.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\util.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\sqlserver.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\spy.jar -export -type=keydb "-expfile=C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/usages_data.xml" -log=UTL_load_usages.log -sid=BID -dsn=jdbc/pool/BID -ssprops=D:/usr/sap/BID/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/BID/SYS/global/security/data/SecStore.key' aborts due to database connection error with return code 64.<br>DIAGNOSIS: The connection parameters are wrong or the database server is shutdown.<br> SOLUTION: Check 'UTL_load_usages.log' and 'C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/UTL.java.log' for more information.
ERROR 2010-09-08 12:12:46
FCO-00011 The step getUsageTypes with step key |NW_Prepare_Export|ind|ind|ind|ind|0|0|NW_Java_Prepare_Export_Dialog|ind|ind|ind|ind|5|0|getUsageTypes was executed with status ERROR .
Could anyone please help me out on this, if possible?
Thanks
JM

Hi,
please ensure that you use a SAP supported JDK as below:
716604 for the Sun JDK (Windows, Linux, Solaris)
709140 Recommended JDK and VM Settings for the WebAS630/640/7.0
And the re try the export pls.
Regards,
Snow

AXL SQL Toolkit - What can I do with creates *.response file?

I used AXL SQL Toolkit with sample.xml input to generate sample.response file with needed data. How now I can open created file with readable view? Thanks

It's a simple text file.. you can open it with any text editor (e.g. notepad on windows.. or vim on linux).
However, I'd recommend that you use the axlsql toolkit just as an example of how you do sql via axl.. and use it as a starting point for your own application. I built my own GUI based sql tool which works a bit like Microsoft's SQL tools - in the end I think that's what every programmer looks for and the axlsqltoolkit is way too clumsy to be used efficiently.

SQL toolkit Win7 connection problem

I'm using CVI 2013 and the SQL toolkit (2.2) tto connect to a mySQL database. I can connect fine using my development computer, but not with the target one. Both computers are running 64-bit Windows 7 Professional (SP1). I was initially using the 64-bit ODBC drivers (mysql-connector-odbc-5.3.2-win64.msi) on both machines. After I had trouble I found a Knowledge Base article that indicated I should probably be using the 32-bit one instead. So I removed the drivers from the target and installed the 32-bit ones using odbcad32.exe found in Windows/SysWOW64. No change.
I'm using the browser2.prj sample project included with the SQL toolkit (by default at: C:\Users\Public\Documents\National Instruments\CVI\samples\sql\apps) to test the functionality of the SQL toolkit. I build a distribution kit including the Shared Run-Time Engine on the development machine and install that on the target. I have traced the problem to the call for DBSources() - it returns a -100 (which, handily, is not amoung the list of database error codes).
On both machines the ODBC drivers appear to be working. I can get to the database using Control Panel->Administrative Tools->Data Sources (ODBC). Selecting the database under either User DSN or System DSN and then clicking Configure will open the MySQL Connector/ODBC Data Source Connection window. Clicking Test in that window will connect to the database.
So the problem seems to lie in the way that CVI connects to the database. I'm clueless at this time, so any suggestions would be greatly appreciated.
Solved!
Go to Solution.

Sorry if this is a stupid question:
Have you followed the instructions in Help->Library Reference->SQL Toolkit Library->SQL Language Reference->Distributing an SQL Toolkit Executable or DLL ?
Or is this an error you are getting despite following those instructions?

Pop up using PL SQL Toolkit

Hello there :
Is there any way we can create a pop-up window using PL/SQL Toolkit.
Thanks for the help.
Regards,
Mohit

using ApEx forum may be more efficient for PL/SQL Toolkit -> Oracle Application Express (APEX)

Mysql database connection with Labwindows/CVI 2009 sql toolkit

Dear experienced users,
I am using the following software/hardware:
Windows 7/ Mysql database 5.6.15 64-bit with MySql ODBC 5.2 Ansi driver installed
Labwindows/CVI 2009 with sql toolkit
The user DSN of ODBC Data source administrator have been confiugred to one of mysql database. The test MYSQL Connector/ODBC is succesful.
The Labwindows/CVI build setting is configure to debug64 after trying debug (32)
The source code is from the example readtab.c with changes to the dsn I am testing
hdbc = DBConnect ("DSN=dvd_collection");
The error message I have is confusing me.
(it is in the attachd png)
I thought it was due to the 64 bit mysql database. That's why I tried the 64 bit build from Labwiondws/CVI. I alsow tried Labview DB tools open connect.vi. It shows me the same error.
Any suggestion is appreciated.
Thanks,
Jimmy
Attachments:
Capture.PNG ‏24 KB

Jimmy
I always use connection strings of the form "DSN=datasourcename;UID=database_user_id; PWD=database_user_password".
Where:
datasourcename = The name of the connection defined in the ODBC connection.
database_user_id = One of the user identities created by the database administrator. Obviously the administrator will lock down the permissions appropriate to the task in hand.
database_user_password = The password that identifies database_user_id, again set by the database administrator.
Note that while it is obviously desireable to lock the permissions down as far as possible on the MySQL server, the more you do so, the slower the database will run, because of the way mySQL searches the permissions tables.

Packed library and SQL Toolkit

Hi
I have labview development studio and I have made some test software that runs a test and posts the results to a database.
I have built the functions of the test in to a packed library
Another company will be using the packed library to test some pcb's for us. The problem is that they do not have the database module in their labview and so the database section of the code does not work.
Is there a run time program for the SQL toolkit I can give them?
Solved!
Go to Solution.

No, but you can replace them with these drivers and not have to worry about toolkits. Be sure to read the discussion too - it will give you other reasons why you are better off without the DCT. The download link for a current version of LV is on the last page of the discussion.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

SQL Toolkit sur Windows x64

Similar Messages

Maybe you are looking for