Archived: LabVIEW Database Connectivity Toolset 1.0.1 Known Issues

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

Overview



This document contains the LabVIEW Database Connectivity Toolset 1.0.1 Known Issues. It includes the set of known issues that have been discovered since the release of of this version of the toolset. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered. Each Issue appears as a row in the table and includes an issue title, a brief description of the problem, any workarounds that might help resolve the issue, and the date the issue was added to the document (not the reported date).

The issues appear in two tables which each contain the same information:

  • Known Issues by Category - This table sorts the issues by category. This table is recommended for use in helping determine if an issue has been reported to us, and is also recommended for users wanting to skim the document to learn of potential issues they may face during development.
  • Known Issues by Date - This table is a flattened list of all issues sorted only by the date the issue was added to the document. Use this table to quickly locate the most recently reported issues.

The workarounds that appear in the document are not always tested by NI and are not guaranteed to resolve the issue. If a workaround refers you to the NI KnowledgeBase, please visit www.ni.com/kb/ and enter that KB number in the search field to locate the specific document. The brief description given does not necessarily describe the problem in full detail, and it is expected that you might want more information on an issue. If you would like more information on an issue feel free to contact NI and referencing the ID number given in the document. You can contact us through any of the normal support channels including phone, email, or the discussion forums. See www.ni.com/ask to contact us. Also consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.



to start the new paragraph within the same set of

  • tags. If you need to indent a list within another list, nest the indented list within the first list's set ofortags. */ P.Indent1 { margin-left:12.00pt; margin-top:6.00pt; margin-bottom:3.00pt; font-family:Verdana; font-size:8pt; color:#000000; } P.Indent2 { margin-left:24.00pt; margin-top:6.00pt; margin-bottom:3.00pt; font-family:Verdana; font-size:8pt; color:#000000; } P.Indent3 { margin-left:36.00pt; margin-top:6.00pt; margin-bottom:3.00pt; font-family:Verdana; font-size:8pt; color:#000000; } /* Use the LI style for all list items. */ LI { margin-top:3.00pt; margin-bottom:3.00pt; font-family:Verdana; font-size:8pt; color:#000000; } /* Use the OL style for numbered lists. You do not have to type the number for each list item in a numbered list. */ OL { margin-left:18.00pt; margin-top:3.00pt; margin-bottom:3.00pt; text-indent:0pt; font-family:Verdana; font-size:8pt; color:#000000; list-style-type: decimal; } /* Use the OL style for numbered lists. Nested lists will use the bullet types according to the nesting scheme below */ ol ol {list-style-type:lower-alpha} ol ol ol {list-style-type:decimal} ol ol ol ol {list-style-type:lower-alpha} ol ol ol ol ol {list-style-type:decimal} ol ol ol ol ol ol {list-style-type:lower-alpha} ol ol ol ol ol ol ol {list-style-type:decimal} ol ol ol ol ol ol ol ol {list-style-type:lower-alpha} /* Use the EquationNum style class for numbered lists of equations. You do not have to type the number for each list item in a numbered list. */ OL.EquationNum { margin-left:36.00pt; margin-top:3.00pt; margin-bottom:3.00pt; text-indent:0pt; font-family:Verdana; font-size:8pt; color:#000000; list-style-type: decimal; } /* Use the List-abc style class for lettered lists. You do not have to type the letter for each list item in a lettered list. */ OL.List-abc { margin-left:18.00pt; margin-top:3.00pt; margin-bottom:3.00pt; text-indent:0pt; font-family:Verdana; font-size:8pt; color:#000000; list-style-type:lower-alpha; } /* Use the UL style for bulleted lists. You do not have to type the bullet for each list item in a bulleted list. */ UL { margin-left:12.00pt; text-indent:0pt; margin-top:3.00pt; margin-bottom:3.00pt; font-family:Verdana; font-size:8pt; color:#000000;} /* Use the List-Box style class for bulleted lists with boxes instead of bullets. You do not have to type the box for each list item in a box list. */ UL.List-Box { margin-left:12.00pt; margin-top:3.00pt; margin-bottom:3.00pt; text-indent:0pt; font-family:Verdana; font-size:8pt; color:#000000; list-style-type: square; } /* Use the Borderless style class for tables that do not need borders, such as for 2-column or 3-column lists with no headings. */ Table.Borderless { border:none; } /* Use the Bordered style class for tables that need borders. */ Table.Bordered { border-width: 1pt; border-style: solid; border-color: #000000; border-collapse: collapse; } /* Use the Borderless-Wide style class for tables that do not need borders and that you want to stretch to fill the entire topic width. */ Table.Borderless-Wide { border:none; width:100%; } /* Use the Bordered-Wide style class for tables that need borders and that you want to stretch to fill the entire topic width. */ Table.Bordered-Wide { border-width: 1pt; border-style: solid; border-color: #000000; width:100%; border-collapse: collapse; } /* Use the TD style for table cells in Borderless or Borderless-Wide tables. */ TD { font-family:Verdana; font-size:8pt; color:#000000; vertical-align:top; padding:3px; } /* Use the Bordered style class for table cells in Bordered or Bordered-Wide tables. */ TD.Bordered { font-family:Verdana; font-size:8pt; color:#000000; vertical-align:top; border-width: 1pt; border-style: solid; border-color: #000000; } /* Use the Icon style class for table cells that contain note, caution, warning, or tip icons, or LabVIEW datatype terminals. */ TD.Icon { width:40px; vertical-align:top; } /* Use the Table-cell-8pt style class for table cells in tables that contain a lot of information and need smaller text to fit it all on one screen to prevent a horizontal scroll bar from appearing. */ TD.Table-cell-8pt { font-family:Verdana; font-size:7pt; color:#000000; } /* Use the TH style for table heading cells in Borderless or Borderless-Wide tables. */ TH { font-family:Verdana; font-size:8pt; color:#000000; font-weight:bold; padding:3px; } /* Use the Bordered style class for table heading cells in Bordered or Bordered-Wide tables. */ TH.Bordered { font-family:Verdana; font-size:8pt; color:#000000; font-weight:bold; border-width: 1pt; border-style: solid; border-color: #000000; } /* Use the Table-cell-8pt style class for table heading cells in tables that contain a lot of information and need smaller text to fit it all on one screen to prevent a horizontal scroll bar from appearing. */ TH.Table-Head-8pt { font-family:Verdana; font-size:7pt; color:#000000; font-weight:bold; } /* Use the Left-Align style class for table heading cells that you want to left align instead of center align. */ TH.Left-Align { font-family:Verdana; font-size:8pt; color:#000000; font-weight:bold; padding:3px; text-align:left; } /***************************************************/ /* CHARACTER FORMATS */ /* The following section defines character formats that every HTML Help project should need. */ /* Use the Dark-Red format for warnings or cautions. */ #Dark-Red { color: #800000 } /* Use the Monospace format for code or syntax examples. */ #Monospace { font-family: Courier New; font-size: 8pt; } /* Use the Monospace-Bold format for messages and responses that the computer automatically prints to the screen. */ #Monospace-Bold { font-family: Courier New; font-size: 8pt; font-weight: bold; } /* Use the Monospace-Italic format to denote text that is a placeholder for a word or value that the user must supply. */ #Monospace-Italic { font-family: Courier New; font-size: 8pt; font-style: italic; } /* Use the Platform format to denote a specific platform. */ #Platform { color: #0000FF; font-weight: bold; } /* Use the Symbol format for characters not in the Verdana character set. Use this format sparingly. When possible, you should use the correct ASCII code for the symbol or use a graphic to recreate the symbol. */ #Symbol { font-family: Symbol; font-size: 8pt; } /***************************************************/ /* ACTIVITY STYLES */ /* The following section defines styles that only tutorial-style HTML Help projects should need. */ /* Use the Activity-Objective style class for the objective at the beginning of an activity topic. */ H3.Activity-Objective { color: #800000; } /***************************************************/ /* CODE STYLES */ /* The following section defines styles that you need to format entire sections of code or syntax examples. If you have just a few words you need to format as a code or syntax example, use the Monospace character format. */ P.Code { margin-top:3.00pt; margin-bottom:0.00pt; font-family:Courier New; font-size:8pt; color:#000000; } P.Code1 { margin-left:12.00pt; margin-top:3.00pt; margin-bottom:0.00pt; font-family:Courier New; font-size:8pt; color:#000000; } P.Code2 { margin-left:24.00pt; margin-top:3.00pt; margin-bottom:0.00pt; font-family:Courier New; font-size:8pt; color:#000000; } P.Code3 { margin-left:36.00pt; margin-top:3.00pt; margin-bottom:0.00pt; font-family:Courier New; font-size:8pt; color:#000000; } /***************************************************/ /* FUNCTION STYLES */ /* The following section defines styles that you might need to format function reference help. */ P.F-VI-Code4 { margin-left:48.00pt; margin-top:3.00pt; margin-bottom:0.00pt; font-family:Courier New; font-size:8pt; color:#000000; } P.F-VI-Code5 { margin-left:60.00pt; margin-top:3.00pt; margin-bottom:0.00pt; font-family:Courier New; font-size:8pt; color:#000000; } P.F-VI-Equation { margin-top:9.00pt; margin-bottom:9.00pt; font-family:Verdana; font-size:8pt; color:#000000; } OL.F-VI-EquationNum { margin-top:3.00pt; margin-bottom:3.00pt; text-indent:0pt; font-family:Verdana; font-size:8pt; color:#000000; list-style-type: decimal; }

Known Issues by Category

The following items are known issues in LabVIEW Database Connectivity Toolkit 1.0.1 sorted by Category.

ActiveX and .NET
4D6EI7XXLabVIEW Throws ActiveX Error 3005
Data Types
3YIB1700Database Toolkit does not Support Timestamp Data Stored in Old Timestamp Format
40DGB184Database variant to data does not work with time stamps
459AA98ZDatabase Variant to Data can not Convert Empty Variant to Numeric Type in 8.2
497B80YTDatabase Insert Item can not Add Variants Correctly in LabVIEW 8.x
Functions, VIs, and Express VIs
2F7E2352Memory Leak in the Database Toolset in DB Tools Open Schema VI
2UJBIC52Can not Insert Timestamp into SQL Database.
2VRETLJ1Database Variant to Data primitive does not support same data types as Variant to Data
3YJAJH00Unable to drop the Database Variant to Data function
Installation/Activation
48BI51LJDatabase Connectivity Toolkit Custom Installation Doesn't Work for Custom Directories
LabVIEW Version Specific
4D9H6IB7Database Connectivity Toolset SQL VIs Will Not Load In LabVIEW 8.5



IDKnown Issue
ActiveX and .NET
4D6EI7XXLabVIEW 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
3YIB1700Database 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
40DGB184Database 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
459AA98ZDatabase 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
497B80YTDatabase 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
2F7E2352Memory 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
2UJBIC52Can 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
2VRETLJ1Database 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
3YJAJH00Unable 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
48BI51LJDatabase 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
4D9H6IB7Database 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

Known Issues by Date

The following items are known issues in LabVIEW Database Connectivity Toolkit 1.0.1 sorted by Date.

4D6EI7XXLabVIEW Throws ActiveX Error 3005
2F7E2352Memory Leak in the Database Toolset in DB Tools Open Schema VI
2UJBIC52Can not Insert Timestamp into SQL Database.
2VRETLJ1Database Variant to Data primitive does not support same data types as Variant to Data
3YIB1700Database Toolkit does not Support Timestamp Data Stored in Old Timestamp Format
3YJAJH00Unable to drop the Database Variant to Data function
40DGB184Database variant to data does not work with time stamps
459AA98ZDatabase Variant to Data can not Convert Empty Variant to Numeric Type in 8.2
48BI51LJDatabase Connectivity Toolkit Custom Installation Doesn't Work for Custom Directories
497B80YTDatabase Insert Item can not Add Variants Correctly in LabVIEW 8.x
4D9H6IB7Database Connectivity Toolset SQL VIs Will Not Load In LabVIEW 8.5



IDKnown Issue
4D6EI7XXLabVIEW 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
2F7E2352Memory 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
2UJBIC52Can 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
2VRETLJ1Database 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
3YIB1700Database 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
3YJAJH00Unable 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
40DGB184Database 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
459AA98ZDatabase 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
48BI51LJDatabase 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
497B80YTDatabase 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
4D9H6IB7Database 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

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).