Sounds like a rights issue... does the user account of your web server have sufficient rights to make changes to the data? Usually Iusr_servername.

>After a few days..yes DAYS, of going around this matter, I take the liberty to go to you as a resort hoping that someone had gone through the same thing, or at least similar. Awaiting for some type of "light" that would help me clear the light-path along this devious road, following I detail something that has been classified as a "cancer" status during my daily work.
>
>
>Enviroment:
>
>OS: Windows XP Professional
>Web Server: IIS 5.0
>Plataform: ASP - VBScript
> DATA ORIGIN: DBC VFP 6.0
>ODBC: Microsoft Visual FoxPro Driver Ver. 6.01.8629.01 (VFPODBC.DLL)
>DSN: System
>
>
>Problem:
>
> It does not matter what type of update I give to any DBF belonging to DBC, I always get the same
>message:
>Microsoft OLE DB Provider for ODBC Drivers error '80004005'
>
>[Microsoft][ODBC Visual FoxPro Driver]Cannot update the cursor.
>
> The Driver in Spanish states: Incompatibilidad en el tipo de datos.
>
> The truth is that ALL the input of data is character and the tables' fields also (logically). Specifically, the last of the intents happens when an "INSERT INTO" is made, just the way it follows:
>
> Dim cConn
>
>Set cConn=Server.CreateObject("ADODB.Connection")
>
>cConn.Mode=adModeReadWrite
>
>cConn.Open "DSN=mercosurindex"
>
>
>MySQL="INSERT INTO sugerencias (des_cate, des_pais, URL, Desc, Nombre, Fecha, email) VALUES ('"
>
>MySQL=MySQL & strCate & "', "
>
>MySQL=MySQL & "'" & strPais & "', "
>
>MySQL=MySQL & "'" & strURL & "', "
>
>MySQL=MySQL & "'" & strDesc & "', "
>
>MySQL=MySQL & "'" & strNombre & "', "
>
>MySQL=MySQL & "'" & strDate & "', "
>
>MySQL=MySQL & "'" & strEmail & "')"
>
>Set RS=cConn.Execute(MySQL) Aqui se produce el error, cuando ejecuta el INSERT INTO
>
>Response.Write(MySql)
>
>cConn.Close
>
>set cConn=nothing
>
>
> I have exhausted all the possibilities and alternatives, since I have tried to change field by field individually, taking away the "date", etc. etc. but it always comes up with the same.
>
>Any ideas? Might it be a bug of the driver.dll?
>Tired...very much tired...... FAB