PDF1. Known Issues by Category
The following items are known issues in LabVIEW Database Connectivity Toolkit 1.0.1 sorted by Category.
| ID | Known Issue |
|---|---|
| ActiveX and .NET | |
| 4D6EI7XX | LabVIEW Throws ActiveX Error 3005 LabVIEW throws ActiveX error 3005 when executing property and invoke nodes that are passed an automation refnum. This is commonly seen in the Database Connectivity Toolset Execute Query VI. Workaround—Use the forward-only cursor type Date Added—09/12/2007 Return to top |
| Data Types | |
| 3YIB1700 | Database Toolkit does not Support Timestamp Data Stored in Old Timestamp Format Timestamps used to be stored as a non-native data type. The toolkit only operates using the native timestamp data type. Workaround—Use a Variant to Data primitive instead Date Added—11/01/2007 Return to top |
| 40DGB184 | Database variant to data does not work with time stamps In 8.0, I could convert a time stamp from a database to a LV time stamp with Database Variant To Data. In 8.20, it gives error 91, "The data type of the variant is not compatible with the data type wired to the type input." Workaround—Replace the "Database Variant to Data" with "Variant to Data". (Does not work with 2D arrays) Date Added—11/01/2007 Return to top |
| 459AA98Z | Database Variant to Data can not Convert Empty Variant to Numeric Type in 8.2 Error -2147467261 occurred at Invalid pointer in Get Parameter Info.vi->Get and Format Parameter Info.vi->Generate Help Documents.vi->Create Help Documents From Database.vi is returned when trying to convert empty variant data to a numeric data type. Workaround—N/A Date Added—11/01/2007 Return to top |
| 497B80YT | Database Insert Item can not Add Variants Correctly in LabVIEW 8.x A low-level Database Toolkit VI used in the writing to database process improperly parses variant types in LabVIEW 8.x. Inserting variants into a database can result in data corruption and/or loss. Workaround—N/A Date Added—11/01/2007 Return to top |
| Functions, VIs, and Express VIs | |
| 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. Date Added—11/01/2007 Return to top |
| 2UJBIC52 | Can not Insert Timestamp into SQL Database. An Insert that uses a timestamp stops working after doing a Select on any database. Workaround—N/A Date Added—11/01/2007 Return to top |
| 2VRETLJ1 | Database Variant to Data primitive does not support same data types as Variant to Data Some of the data types supported by the polymorphic Variant to Data are not supported i the Database Variant to Data primitive. Workaround—N/A Date Added—11/01/2007 Return to top |
| 3YJAJH00 | Unable to drop the Database Variant to Data function If the Database Connectivity Toolkit 1.0 is installed, you cannot place the Database Variant to Data function on the block diagram. This is the same issue as 3YJ9J200 . Workaround—Refer to KnowledgeBase 3YJAJH00 at ni.com for more information about correcting this problem. Date Added—11/01/2007 Return to top |
| Installation/Activation | |
| 48BI51LJ | Database Connectivity Toolkit Custom Installation Doesn't Work for Custom Directories When you install the Database Connectivity Toolkit, if the custom option is selected, it's supposed to be installed to the directory of the user's choice. However, this results in the Toolkit being installed to [chosen directory]\[most current LV version]. Workaround—Manually copy the installed components from the ...\LabVIEW [latest version]\ folder to their respective LabVIEW version folders. Date Added—11/01/2007 Return to top |
| LabVIEW Version Specific | |
| 4D9H6IB7 | Database Connectivity Toolset SQL VIs Will Not Load In LabVIEW 8.5 The Database Connectivity Toolset SQL VIs will not load in LabVIEW 8.5. These SQL VIs are still included with the toolkit for backwards compatibility. Workaround—Either: A. Mass compile the _SQL directory of the Database Connectivity Toolset in LabVIEW 8.0 or 8.2 and then copy the directory to the corresponding LabVIEW 8.5 directory. Contact National Instruments Support if you do not have either of these LabVIEW versions. B. Convert to using the Database Connectivity VIs instead of the included SQL VIs. Date Added—11/01/2007 Return to top |
2. Known Issues by Date
The following items are known issues in LabVIEW Database Connectivity Toolkit 1.0.1 sorted by Date.
| ID | Known Issue |
|---|---|
| 4D6EI7XX | LabVIEW Throws ActiveX Error 3005 LabVIEW throws ActiveX error 3005 when executing property and invoke nodes that are passed an automation refnum. This is commonly seen in the Database Connectivity Toolset Execute Query VI. Workaround—Use the forward-only cursor type Date Added—09/12/2007 Return to top |
| 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. Date Added—11/01/2007 Return to top |
| 2UJBIC52 | Can not Insert Timestamp into SQL Database. An Insert that uses a timestamp stops working after doing a Select on any database. Workaround—N/A Date Added—11/01/2007 Return to top |
| 2VRETLJ1 | Database Variant to Data primitive does not support same data types as Variant to Data Some of the data types supported by the polymorphic Variant to Data are not supported i the Database Variant to Data primitive. Workaround—N/A Date Added—11/01/2007 Return to top |
| 3YIB1700 | Database Toolkit does not Support Timestamp Data Stored in Old Timestamp Format Timestamps used to be stored as a non-native data type. The toolkit only operates using the native timestamp data type. Workaround—Use a Variant to Data primitive instead Date Added—11/01/2007 Return to top |
| 3YJAJH00 | Unable to drop the Database Variant to Data function If the Database Connectivity Toolkit 1.0 is installed, you cannot place the Database Variant to Data function on the block diagram. This is the same issue as 3YJ9J200 . Workaround—Refer to KnowledgeBase 3YJAJH00 at ni.com for more information about correcting this problem. Date Added—11/01/2007 Return to top |
| 40DGB184 | Database variant to data does not work with time stamps In 8.0, I could convert a time stamp from a database to a LV time stamp with Database Variant To Data. In 8.20, it gives error 91, "The data type of the variant is not compatible with the data type wired to the type input." Workaround—Replace the "Database Variant to Data" with "Variant to Data". (Does not work with 2D arrays) Date Added—11/01/2007 Return to top |
| 459AA98Z | Database Variant to Data can not Convert Empty Variant to Numeric Type in 8.2 Error -2147467261 occurred at Invalid pointer in Get Parameter Info.vi->Get and Format Parameter Info.vi->Generate Help Documents.vi->Create Help Documents From Database.vi is returned when trying to convert empty variant data to a numeric data type. Workaround—N/A Date Added—11/01/2007 Return to top |
| 48BI51LJ | Database Connectivity Toolkit Custom Installation Doesn't Work for Custom Directories When you install the Database Connectivity Toolkit, if the custom option is selected, it's supposed to be installed to the directory of the user's choice. However, this results in the Toolkit being installed to [chosen directory]\[most current LV version]. Workaround—Manually copy the installed components from the ...\LabVIEW [latest version]\ folder to their respective LabVIEW version folders. Date Added—11/01/2007 Return to top |
| 497B80YT | Database Insert Item can not Add Variants Correctly in LabVIEW 8.x A low-level Database Toolkit VI used in the writing to database process improperly parses variant types in LabVIEW 8.x. Inserting variants into a database can result in data corruption and/or loss. Workaround—N/A Date Added—11/01/2007 Return to top |
| 4D9H6IB7 | Database Connectivity Toolset SQL VIs Will Not Load In LabVIEW 8.5 The Database Connectivity Toolset SQL VIs will not load in LabVIEW 8.5. These SQL VIs are still included with the toolkit for backwards compatibility. Workaround—Either: A. Mass compile the _SQL directory of the Database Connectivity Toolset in LabVIEW 8.0 or 8.2 and then copy the directory to the corresponding LabVIEW 8.5 directory. Contact National Instruments Support if you do not have either of these LabVIEW versions. B. Convert to using the Database Connectivity VIs instead of the included SQL VIs. Date Added—11/01/2007 Return to top |
