>>Hi all,
>>Is there a problem with VFP7 OLEDB provider when using recordset.Update method in an ASP? We get an error when trying to set a value in the first field: rs.field("username")="sam"
>>Message says something like "...either provider cannot process request or change locking method." We've tried unsuccessfully to get past this one.
>
>Try to make the recordset clien side

>rs.CursorLocation = ADUSECLIENT

>< snip >

Tried both server side and client side cursor (and various combinations of cursor type and lock type). Still having same problem with rs.update. I'm using PWS on NT4 and ODBC. Another tried it on a notebook (VFP7) with OLEDB and ODBC. He gets error stated above using OLEDB and "query based update failure..." using ODBC.
He and I get "query based update failure..." on our desktops using VFP6 and ODBC; he gets error first time, I get it 2nd or third time never first time.

Never have a problem using SQL UPDATE statement, but would really want to use rs.update (code readability, debugging, > 254 chars into memo field, etc).