石鑫华视觉
Windows系统下（Linux和MAC系统下请自行了解清楚）NI的各种软件、模块、工具包、驱动程序，使用NI许可证管理器来激活的，绝大部分的都可以使用NI Lincense Activator来激活：NI序列号Serial Number生成激活工具NI License Activator，LabVIEW/VBAI/VDM/VAS等软件模块工具包破解工具不限版本http://pcmv.cn/thread-490-1-1.html
视觉论坛的各种NI资源，除了视觉相关的模块有使用外，大部分的都不会使用，仅提供资源不提供技术支持。资源的下载地址一般会同时提供NI官方和百度网盘的地址。某些工具包NI地址失效或没有NI地址，只能使用百度网盘地址；如果百度网盘地址失效过期，可联系论坛客服更新。NI的服务器在美国，有时候速度很慢或下载容易出错，这样会造成安装时各种错误而无法安装。建议在下载完成后，对下载资源做校验和(NI一般会提供MD5或SHA256等)验证，与官方或视觉论坛提供的校验和对比，一致就可以安装；如不一致，则需要重新下载。视觉论坛早期下载上传的资源，基本上都是正常下载的资源；2019后下载的资源，都与NI的正确校验和对比过，保证是正确的资源才上传到百度网盘。校验和工具下载地址：文件Hash计算器FHash，文件校验和验证下载文件正确性验证，MD5值计算、SHA1值计算、SHA256值计算、CRC32值计算http://pcmv.cn/thread-26524-1-1.html
NI LabVIEW 8.6 Database Connectivity Toolkit Win32Eng LV8.6数据库连接工具包DCT1.0.2
数据库工具包，后面的几代版本的LabVIEW中，在安装时就已经包含在LabVIEW(专业版)内部，可以在安装时直接选择安装数据库连接工具包，不需要再单独下载安装，如果早期的版本没有包含数据库工具包，则可以下载该独立版本。也可以使用第三方的免费的LabSQL工具包。
百度网盘下载链接：
请注册视觉论坛会员登录后购买附件下载查看
NI LabVIEW 8.6 Database Connectivity Toolkit Win32Eng LV8.6数据库连接工具包DCT1.0.2
http://pcmv.cn/thread-22412-1-1.html?fromuid=9
(出处: 机器视觉论坛)
LabVIEW Database Connectivity Toolkit 1.0.2 Readme
System Requirements
Windows Vista/XP/2000
A minimum of 40 MB free disk space
LabVIEW 8.6
Installation Instructions
Log on as an administrator or as a user with administrator privileges.
Insert the LabVIEW Database Connectivity Toolkit 1.0.2 installation CD and follow the instructions that appear on the screen.
Activate your LabVIEW products using the NI License Manager.
Version 1.0.1 for LabVIEW 6.x, 7.x, or 8.x
Log on as an administrator or as a user with administrator privileges.
Insert the LabVIEW Database Connectivity Toolkit 1.0.2 installation CD and browse to the LabVIEW_6.0-8.5 directory.
Double-click setup.exe and follow the instructions that appear on the screen.
Recommended Database Client Software
Microsoft Access— National Instruments recommends that you use the Microsoft Jet 4.0 or later OLE DB Provider.
Microsoft SQL Server—National Instruments recommends that you use the Microsoft OLE DB Provider for SQL Server.
Oracle 7 and 8—You must install Oracle Client software on the machine to which you install the Database Connectivity Toolkit. National Instruments recommends that you use the Oracle Provider for OLE DB 8.1.6.2.0 or later. You can download the Oracle Provider from the Oracle Web site at www.oracle.com.
Accessing the Help
Launch LabVIEW.
Select Help»Search the LabVIEW Help from the pull-down menu to launch the LabVIEW Help.
Click the Contents tab.
Navigate to Toolkits»Database VIs and Function.
Finding Examples
Known Issues
The Microsoft ODBC driver for Oracle and the Microsoft OLE DB Provider for Oracle do not support BLOB, or binary, data types. You cannot use Oracle with the Database Connectivity Toolkit for binary data with these drivers. Use the OLE DB Provider and ODBC driver that Oracle provides instead. You can download the Oracle DB Provider and ODBC driver from the Oracle Web site at www.oracle.com.
When you read data from an Oracle database, data types of NUMBER do not show up in the variant indicator. This data is available but not visible. To see NUMBER data, use the Database Variant To Data function to convert the NUMBER to a string or to any numeric data type in LabVIEW.
If the Microsoft Access ODBC driver and Jet Provider return the error Operation canceled, verify that the ODBC data source and/or data link connection string reference a valid .mdb file.
The Microsoft Jet 4.0 OLE DB Provider and ODBC Driver might return the following error message when two executions attempt to gain write access to the same table.
Native error code -2147467259 0x80004005
Microsoft JET Database Engine:
Could not update; currently locked by user 'Admin' on machine 'XXX'.
This problem occurs if each execution or thread opens a unique connection to the database or opens unique statements to a table. In other words, this problem occurs if the executions or threads do not share handles. The Microsoft Access drivers use a lazy file access method that can cause this error. If this error occurs while you are accessing a Microsoft Access database from multiple processes or different computers, you must attempt to recover from this error and retry the failing database action.
Inserting BLOB data into dBASE databases does not work if you use the OLE DB Provider for ODBC with an ODBC Data Source that points to a dBASE DSN. Refer to the Microsoft KnowledgeBase article Q264242 for a workaround.
Asking for a dynamic cursor using the Microsoft Jet 4.0 OLE DB Provider gives a static cursor that is not quite correctly implemented. This bug has been reported to Microsoft.
The Microsoft FindFast utility sometimes prevents writing to files. This problem results in an Access Denied error message. Disable FindFast by removing it from the startup group in the Program Files menu and reboot the computer.
You might experience slow performance when reading the entire contents of a large database table into LabVIEW. National Instruments does not recommend that you work with very large recordsets because doing so is inefficient and uses a large amount of computer resources. However, the Database Connectivity Toolkit does provide the Read All Data example VI that demonstrates how to return a large amount of table data into a 2D array of strings in the most efficient method ADO provides.
The Read All Data example VI uses few resources to return recordset data. However, this VI also has some limitations because the data format is a 2D array of strings. You must convert these strings into the LabVIEW data types that are most useful for displaying that data. Binary data such as arrays and clusters must be unflattened or type cast to their original format.
The Read All Data example VI also is unable to read recordsets that contain a NULL value anywhere in the resulting recordset. LabVIEW returns no data and generates an error.
The Database Connectivity Toolkit demo, available by selecting Start» Programs»National Instruments»LabVIEW Database Connectivity Toolkit»Database Connectivity Demo or by navigating to the labviewexamplesdatabaseTelecommunications Parametric Testing.llb, does not work with the LabVIEW Base Package because some of the testing VIs use advanced analysis functions available only in the LabVIEW Full and Professional Development Systems.