10-05-2005 10:26 AM
10-05-2005 11:02 AM
10-07-2005 10:54 AM
Marcelo & ramji,
This error is actually being generated by the ODBC drivers. I've spent some time researching it on the web, and it looks like it in all sorts of programming languages and applications. Unfortunately, I didn't find a solution or workaround for the error. I searched the Microsoft KnowledgeBases and didn't find any relevant to this particular error so I have submitted the question to Microsoft support. You may want to do this as well. I will certainly post any information I hear back from them.
Good luck!
Megan B.
National Instruments
10-10-2005 12:16 PM
10-10-2005 12:18 PM
10-11-2005 02:58 PM
Hi Marcelo,
Sorry about that, I had a lapse of focus. You are right that this is unlikely to be a Microsoft problem. However, it still looks like it is an issue with the ODBC drivers. Searching google I've found people encountering the same error in Python:
http://groups.google.com/group/mailing.database.myodbc/browse_thread/thread/635e32bd80aefb88/e4b7659...)
and more
http://groups.google.com/group/mailing.database.myodbc/browse_thread/thread/406ef72aab160032/5e9ed45....
The easiest thing may be to check for this error and try to handle it in LabVIEW (perhaps just clear it and redo the database operation).
Megan B.
National Instruments