> Hi!

> Why I can edit data in SQL Server 7.0 only when I open ADO recordset
> that uses server-side cursor and that is opened as a keyset? I can't use
> client-side cursors because I can't update data in updatable views that
> base on tables that user can't access.

> I would like to use client-side cursors because of ADO error "Consumer's
> event handler called a non-reentrant method in the provider.". I got
> information that I have to use client-side cursors, but they won't let
> me edit my data. What I have to do?

> Greetings,
> Gunnar Peipman

>     Set mCmd = New ADODB.Command
>         mCmd.ActiveConnection = pConn
>         mCmd.CommandText = strSql
>         mCmd.CommandType = adCmdText

>     Set mrstOrderLines = New ADODB.Recordset
>         mrstOrderLines.CursorLocation = adUseClient
>         mrstOrderLines.Open mCmd, , adOpenStatic, adLockOptimistic

> Note the Open Static and adLockOptimistic

> Default recordset is Locked, forward only

> Regards

> VOrtex

> > Hi!

> > Why I can edit data in SQL Server 7.0 only when I open ADO recordset
> > that uses server-side cursor and that is opened as a keyset? I can't use
> > client-side cursors because I can't update data in updatable views that
> > base on tables that user can't access.

> > I would like to use client-side cursors because of ADO error "Consumer's
> > event handler called a non-reentrant method in the provider.". I got
> > information that I have to use client-side cursors, but they won't let
> > me edit my data. What I have to do?

> > Greetings,
> > Gunnar Peipman