FiveTech Software tech support forums

... de Pedidos!", oApp:cAplicacion) ShowError(oError) orsPed := NIL lret:=.f. CLOSE_DBF(ODTEMP) RETURN(lret) END orsPed:CursorLocation := adUseClient orsPed:LockType := adLockOptimistic orsPed:CursorType := adOpenDynamic orsped:source:="SELECT * FROM ERP6_base" // ENVIAMOS QUERY ...

... de Pedidos!", oApp:cAplicacion) ShowError(oError) orsPed := NIL lret:=.f. CLOSE_DBF(ODTEMP) RETURN(lret) END orsPed:CursorLocation := adUseClient orsPed:LockType := adLockOptimistic orsPed:CursorType := adOpenDynamic orsPed:Source :="select * from BasedeDatos" orsPed:ActiveConnection( ...

... de Pedidos!", oApp:cAplicacion) ShowError(oError) orsPed := NIL lret:=.f. CLOSE_DBF(ODTEMP) RETURN(lret) END orsPed:CursorLocation := adUseClient orsPed:LockType := adLockOptimistic orsPed:CursorType := adOpenDynamic orsped:source:="SELECT * FROM ERP6_base" // ENVIAMOS QUERY ...

... de Pedidos!", oApp:cAplicacion) ShowError(oError) orsPed := NIL lret:=.f. CLOSE_DBF(ODTEMP) RETURN(lret) END orsPed:CursorLocation := adUseClient orsPed:LockType := adLockOptimistic orsPed:CursorType := adOpenDynamic orsped:source:="SELECT * FROM ERP6_base" // ENVIAMOS QUERY ...

... information to all of u: Whatever value we specify for oRs:CursorType, ADO invariably opens the recordset as adOpenStatic only for CursorLocation adUseClient. There is not point in assigning a value like adOpenKeySet or adOpenDynamic

Hola Carlos el recordset se abre en modo adUseClient (modo 3) como puedes ver en el modulo, y adLockOptimistic, el problema surge cuando despues de recorrer y grabar el primer registro del recordset, ya no se puede mover hacia ningun lado, da ...

but "save" seems not work

Try inline edit.

Any valid ADO recordset is recognized as RecordSet.

To start with just use

Code: Select all  Expand view

XBROWSER oRs FASTEDIT

Try to add CursorLocation of connection object also as adUseClient.'

... .f. This is a synthetic recordset and has no server and no physical table and no physical indexes. So this recordset's CursorLoction property is adUseClient. Even oRs:ActiveConnection is NIL, because this is not connected to any server. Being a profuse user of indexes and seek, you are aware ...

... oRsDir := TOleAuto():New( "ADODB.RecordSet" ) WITH OBJECT oRsDir :ActiveConnection := oApp:oCon :Source := cSql :CursorLocation := adUseClient :LockType := adLockOptimistic :CursorType := adOpenDynamic TRY :Open() CATCH FW_ShowAdoError( oApp:oCon ) END END oRsDir:Properties("Unique ...

... ) CATCH oError MsgStop( "No se ha podido crear el OBJETO"+ oError:Description ) RETURN .F. END oRSet:CursorLocation:=adUseClient;oRSet:LockType:=adLockReadOnly;oRSet:CursorType:=adOpenForwardOnly;oRSet:ActiveConnection( oConnection ) sSQLQuery := "SELECT * FROM ...

CursorLocation 1 adUseNone (Obsolete and does not work) 2. adUseServer (Can not navigate and is not useful for us) 3. adUseClient : This is the only choice we have LockType: 1. adLockUnspecified (not to be used for new recordsets) 2. adLockReadOnly : This is not what you want when ...

CursorLocation 1 adUseNone (Obsolete and does not work) 2. adUseServer (Can not navigate and is not useful for us) 3. adUseClient : This is the only choice we have LockType: 1. adLockUnspecified (not to be used for new recordsets) 2. adLockReadOnly : This is not what you want when ...

... FALSE Try If lNew // New way... // Suggested by Rick Lipkin from the FW Tech Board. oRs:CursorType := 1 // adOpenKeyset oRs:CursorLocation := 3 // adUseClient oRs:LockType := 3 // adLockOptimistic Else oRs:CursorType := adOpenDynamic oRs:CursorLocation := adUseClient oRs:LockType := adLockOptimistic ...

... the recordset. In other words, it is just useless and meaningless for us to specify a cursor type while openining a recordset with cursorlocation adUseClient. This has been the behavior since ADO was created. There is nothing surprising or unusual about it. Again, it is not that ADO was made like ...

... called a server-side cursor when these resources are located on the server. Client-Side Cursors In ADO, call for a client-side cursor by using the adUseClient CursorLocationEnum. With a non-keyset client-side cursor, the server sends the entire result set across the network to the client computer. ...