error -2147217900 when using Access 2000 - 2003

[Toro]

Hello:  I have been trying to write data to an Access 2003 database. I have search for samples and have try all samples but no matter what I do I get the same result see attach.  I went to Microsoft and foun that -214721763  to -214721plus  is an error for Networking in msdn2.microsoft.com. I have try using Jet engine 4.0, Microsoft Access ODBC, and LabView ODBC. It seems that the sql stament been use  does not work with access.

[mikeporter]

How are you actually connecting to the database? The connectivity toolkit? What is the SQL you are trying to execute? Do any statements work? What is the connection string you are using to connect to the database?

Mike...

[Hillary_C_E]

Hi Toro,

You might also want to check this KB or this one. It seems like your input isn't correct for what your database is expecting.

[Toro]

Hello Everyone:

Thanks

[Toro]

Hello Everyone:

Thanks for

[Toro]

sorry.. pressed wrong key(s).

Hello Everyone:

Thanks for your responds. I found the problem and I have correct it. I was a bit tired of trying everything I can think of and searching for a solution. I though about this so I try re-wrote the pogram in LabView 6.1 and be hold it work fine, so I got me thinking whna could be possibly creating this issue  after a bit of though I remember that when I was installing LabView 8.5 ToolKit  it display some error windows for LabView/CVI and Database Tool 1.01 that I though I have taking care of or the installation did......... so I reinstall LabView 8.5 ToolKit ......

This time it when trough without a problem I allso make sure that the MDAC 2.5 was install. When the installetion for the database come up it ask me for Modify, Repear or Remove  I selected Modify the it show that the MDAC was mark for no down load so I select it for download. Now the database is working properly.

I did not think of reinstalling the toolkit at the beginning because the othe SubVI for reading the database (wich it reads 50 columns) work fine with no issues so I though writting to the database should work hummmm...... a bit pasull!! 

Once agian thanks for your responds