This document contains the LabVIEW 2020 Database Connectivity Toolkit known issues that were discovered before and since the release of LabVIEW 2020 Database Connectivity Toolkit. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.
Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 225366 | 618979 |
No error is returned if an empty 2D array of variants is passed to the Database Variant to Data VIIn other cases, if an empty variant data type is passed to the Database Variant to Data VI, error 91 is returned. This error does not occur if a 2D array of variants is passed to the Database Variant to Data VI.
Workaround: Check for empty arrays before the Database Variant to Data function.
|
Reported Version: Database Connectivity Toolkit 2016 Resolved Version: N/A Added: May 21, 2017 |
| 849887 | 347325 |
DB Tools Insert Data.vi does not write dates correctly when OS language is set to French date formatWhen Windows language format is set to French with the short date to dd/mm/yyyy, the DB Tools Insert Data.vi writes incorrect values to database files.
Workaround: Convert timestamp data into strings before inserting into the database with the DB Tools Insert Data.vi.
|
Reported Version: Database Connectivity Toolkit 2011 Resolved Version: N/A Added: Nov 15, 2012 |
| 849897 | 389996 |
Error 1 Returned from DB Tools Insert Data.viError will be returned when writing array data to MS Access database, and column values are provided despite the database already having column values.
Workaround: There is currently no known workaround for this issue.
|
Reported Version: Database Connectivity Toolkit 2011 Resolved Version: N/A Added: Aug 1, 2013 |
| 882284 | 575865 |
Adding a "Date/Time" column using DB Tools Create Table and a MySQL database creates a column of date onlyWhen using the DB Tools Create Table function to create a new table on a MySQL database and using a "Date/Time" column as one of the column types, the column created is only storing the date.
Workaround: Use a DB Tools Execute Query function to add a column to the table of the correct type using SQL Code after creating the table.
|
Reported Version: Database Connectivity Toolkit 2015 Resolved Version: N/A Added: Aug 7, 2016 |
| 882313 | 580060 |
When using the SQL Server Native Client 10.0 provider, authentication occurs through Windows Integrated Security Authentication rather than through SQL Server AuthenticationWhen the SQL Server Native Client 10.0 provider is used to connect to a database, authentication defaults to Windows Integrated Security Authentication. If an incorrect username and password combination exists in the UDL file, it is still possible for authentication to succeed through Windows Integrated Security Authentication.
Workaround: Use the "Microsoft OLE DB Provider for SQL Server" provider.
|
Reported Version: Database Connectivity Toolkit 2015 Resolved Version: N/A Added: May 21, 2017 |
| 885858 | 642656 |
Using "Connect to ACCDB Database" Example crashes when run multiple times with Access Database Engine 2016When you run the "Connect to ACCDB Database" Example to connect to example "Access2007.accdb" database, LabVIEW will crash if you run the VI multiple times.
Workaround: Change the VI to prompt the user to configure the connection. After completing the prompt steps once, you can reconnect the connection information string and no longer see the crash.
|
Reported Version: Database Connectivity Toolkit 2016 Resolved Version: N/A Added: May 21, 2017 |
| 320264 | 724217 |
LabVIEW crashes with Access DB 2016 installedWhen using 64-bit LabVIEW with Access DB 2016 installed, the database provider will cause LabVIEW to crash.
Workaround: Add the following token to LabVIEW.ini: EnableMS2016AccessProviderSupport=True
|
Reported Version: Database Connectivity Toolkit 2019 Resolved Version: N/A Added: May 16, 2019 |
Issues found in this section will not be listed in future known issues documents for this product.
There are currently no issues to list.
Explore Support Content and Product Documentation
Ask the NI Community
Request Support from an Engineer
A valid service agreement may be required, and support options vary by country