FiveTech Software tech support forums

Please see your code oRs := FW_OpenRecordSet( oDg, "Marcas", adLockBatchOptimistic )  If you change it as oRs := FW_OpenRecordSet( oDg, "Marcas" )//ORoRs := FW_OpenRecordSet( oDg, "Marcas", adLockOptimistic )// ...

... veo que en la BD no queda reflejado nada y tampoco da error. Saben que ocurre?. Alguna solución? oRs := FW_OpenRecordSet( oDg, "Marcas", adLockBatchOptimistic ) DEFINE FONT oFont NAME "TAHOMA" SIZE 0,-12 DEFINE WINDOW oDlg MDICHILD OF WndMain() TITLE cTitulo @ 0,0 XBROWSE oBrw ...

... ) make the changes to the underlying database immediately and are visible to other users on the network. We can also open the recordset using adLockBatchOptimistic mode. oRs := FW_OpenRecordSet( oCn, cSql, adLockBatchOptimistic )  In this case, all changes including methods Update(), ...

... is useful when you read data not to be modified) 3. adLockPessimistic : We need to lock each record for modification. Rarely anybody uses it. 5. adLockBatchOptimistic: Useful. But for more advanced users. 4. adLockOptimistic: This is the only choice we have CursorType: 0. adOpenForwardOnly : ...

... is useful when you read data not to be modified) 3. adLockPessimistic : We need to lock each record for modification. Rarely anybody uses it. 5. adLockBatchOptimistic: Useful. But for more advanced users. 4. adLockOptimistic: This is the only choice we have CursorType: 0. adOpenForwardOnly : ...

... doesn't appear anymore I tried also to set locktype to adLockPessimistic ( in adordd , oRecordSet:Open( ....,2,...) ) This result in locktype 4 (adLockBatchOptimistic) Frank I am afraid that when i can not resolve this issue , i can not use adordd. Frank

... a bit complex. Yet all this is possible only if the data-source being browsed supports this feature. Examples are Arrays, RecordSets opened with adLockBatchOptimistic lock. FWH RowSet supports this feature. Not only it supports but also takes away totally the burden of writing this complex code. ...

... so far. I am eager to learn if a working sample is posted to do this. To achieve the same objective I adopt 2 alternatives: 1) Open with locktype adLockBatchOptimistic and never use oRs:UpdateBatch function Test()   local oCn, oRs   oCn   := FW_OpenAdoConnection( "testins.mdb" ...

... :update() each time. This might be the reason of taking so long? Oh, it absolutely is the reason. Do you mean we should change the :cursorType to adLockBatchOptimistic start a transaction and :updatebatch only at the end? Well it does seem that there is very little chance of someone else trying ...

... record. Both these functions call :update() each time. This might be the reason of taking so long? Do you mean we should change the :cursorType to adLockBatchOptimistic start a transaction and :updatebatch only at the end? May be there is a bug in locks as it should in COPY TO open the destination ...

... results because we lose the benefit of snap-shot query benefits. What we mostly use is RecordSet with adUseClient with either adLockOptimistic or adLockBatchOptimistic. All this is static information as at the time when we executed the query. The recordset does not get updated on its own unless ...

... for AS/400 and VSAM and the Microsoft OLE DB Provider for DB2. However, the OLE DB Provider for AS/400 and VSAM internally maps this lock type to adLockBatchOptimistic. and The adLockPessimistic setting is not supported if the CursorLocation property is set to adUseClient. If an unsupported value ...

... ADO SYNTAX Instead of oRs := TOleAuto():New( "ADODB.RecordSet" ) Use oRs := TRecSet():New() WITH OBJECT oRs // optionally :LockType := adLockBatchOptimistic .... END oRs:Open( [cSql], [oCn], ..... ) // Syntax exactly same as ADO syntax Field values can be accessed and assigned as Data. ...

... now. There was a bug when creating the attached file name of the PDF. Thanks to Lucas! * XBrowse.prg: While browsing a recordset opened with adLockBatchOptimistic, the browse stays stable even if connection to server is lost. Any edits during the browse are not saved to the Server. After ...

... itself and offer inline edit, you need to consider the following implications. As you are aware you can open a recordset with adLockOptimistic or adLockBatchOptimistic. In the first case, once you call oRs:AddNew(), you can not navigate the recordset unless you either Update() or CancelUpdate() ...