04-18-2011 05:14 AM
Hi,
I want to interface LabVIEW2010 and Microsoft Access 2003 by using UDL technique. I am using Microsoft Jet 4.0 OLE DB Provider for this interface. When I Run the sample program, its showing an error Error -2147217900 as follows:
(occurred at NI_Database_API.lvlib:Conn Execute.vi->NI_Database_API.lvlib:DB Tools Create Table.vi->NI_Database_API.lvlib:DB Tools Create Table If Not Exist.vi->NI_Database_API.lvlib:DB Tools Insert Data.vi->Untitled 1.vi)
Possible reason(s):
ADO Error: 0x80040E14
Exception occured in Microsoft JET Database Engine: Syntax error in field definition. in NI_Database_API.lvlib:Conn Execute.vi->NI_Database_API.lvlib:DB Tools Create Table.vi->NI_Database_API.lvlib:DB Tools Create Table If Not Exist.vi->NI_Database_API.lvlib:DB Tools Insert Data.vi->Untitled 1.vi
This error is not consistent, I mean it occurs most of the times, but few times it just disappears 🙂 I have searched a lot on the NI site but not getting any solution. Please help me to solve this error.
Note: I have attached my sample VI named 'Untitled 1' .
04-18-2011 09:52 AM
The problem is most likely in the naming of your table or field names.
You may be using a reserved word or need to use a delimiter to handle table or field names containing a space.
http://www.adopenstatic.com/faq/80040e14.asp
06-19-2015 03:38 AM
may be your creating same table multiple time with same name . please try different table name during each run of Vi . it will work.
06-19-2015 05:33 AM
03-12-2019 02:39 AM
In my case, error 0x80040E14 was generated inside "DB Tools Select Data.vi".
What solved the error for me was adding brackets [ ] around the names of the columns. For example, I was getting the error when reading columns "Index" and "Date", but the error went away when reading [Index] and [Date].
The "table" input works with or without brackets, e.g. both "table_name" and "[table_name]" work.
07-13-2020 12:34 PM
It is possible that you have spaces in the column names. Regardless, place brackets like this [field1], [field2], [field3] for the column names (meaning the array of strings that attaches to the "columns" terminal). This should fix the issue.