Your code below states a VFP 3 table. Which are you using VFP 3 or 6?? What ODBC Driver version are you using??



>Server - IIS 4.0 / NT4.0 / Latest VFP ODBC Drivers
>Client - Win95 / Visual Interdev 6.0 / VFP 6.0 / IE 4.0
>
>
>SQLStatement = "SELECT connection, entrydate, title, name, organizati, workphone, fax, email, website, speed, appearance, navigation, info, rating, comment FROM feedback"
>
>Recordset2.AddNew
>Recordset2("Name") = name
>Recordset2("entrydate") = date()
>Recordset2("Title") = title
>Recordset2("Organizati") = organization
>Recordset2("Workphone") = contact_workphone
>Recordset2("Fax") = contact_fax
>Recordset2("Email") = contact_email
>Recordset2("Website") = contact_url
>Recordset2("Appearance") = Appearance
>Recordset2("Navigation") = Navigation
>Recordset2("Info") = findinfo
>Recordset2("Rating") = overall
>Recordset2("Speed") = speed
>Recordset2("Connection") = connection
>Recordset2("comment") = Request.Form("comments") '<------Comment field is a memo field in a VFP 3.0 table
>Recordset2.Update
>
>
>On the update it returns "errors occured" line xx which is the Resordset2.Update line. As soon as I remove the
>"Recordset2("comment") = Request.Form("comments")" line everything works, and the database updates. I have also tried changing the field to a text size 245 which works but isnt long enough.
>
>So this leaves us at why in ODBC for Visual Foxpro tables does asp/odbc allow me to view but not update a memo field? Do I need to use special characters around the field name in the sql statement ?
>
>Any help would be appreciated.
>
>Thanx,
>Patrick Davis
>For Rob Hawthorne