FiveTech Software tech support forums

Ok, my mistake. I was right AND I was wrong. You can turn off buffering, but not by changing the class variable lBuffer directly. You must do it this way:

oDBF:setBuffer(.F.)

Technically, lBuffer should be a hidden variable that cannot be changed by the programmer. OOP languages like Smalltalk, do ...

oLotto:= TDatabase():Open( , cDir+"Lotto", "DBFCDX", .T. )
oLotto:setorder(nOrder)
oLotto:gotop()
oLotto:lbuffer:=.f.

Turn off buffering.

oDBF:lBuffer:=.f.

If oDbf:lBuffer is .T. (this is the default), changes are saved only if we execute oDbf:Save() and otherwise not saved.

If oDbf:lBuffer is set to .f., then any changes made are written to the dbf.

Actually there is no need to call oDbf:load() specifically in the program. This is done automatically ...

DATAS

1. aBuffer ( ReadOnly Type: "A" ): Array holding the field values of the current record when ::lBuffer is .T.

2. aFldNames ( ReadOnly Type: "A" ): Array containing field names of DBF

3. aStruct ( ReadOnly Type: "A" ): Structure of the table, similar to DBSTRUCT(). aStruct has additional ...

Differences:
1) Your code has
ON CHANGE oDbfr:load().
I omitted this because for TDataBase, the DATA lBuffer is .T. by default. So every skip automatically loads the record and this statement is not necessary.

2) Your code:
FOR nCCol := 1 TO LEN( ::oBrw:acols )
::oBrw:aCols[nCCol]:nHeadStrAlign ...

... Using Tdatabase() is new to me and the burning question is, what setup is needed
to use your example in a multiuser environment. ( lShared, lBuffer ? ).
Is there a sample somewhere, I could reference ?

Gratefully,
Bruce S.
TDatabase by default is set for multiuser use and is buffered.
I ...

... compiles and runs fine.
I will implement it in my code and persue.
-------

Using Tdatabase() is new to me and the burning question is, what setup is needed
to use your example in a multiuser environment. ( lShared, lBuffer ? ).
Is there a sample somewhere, I could reference ?

Gratefully,
Bruce S.

CUSTOMER->( DBGOTO( 200 ) )

This is to prevent the buffer from being reloaded.

Another way you could do it:

oDBF:lBuffer:=.f.
oDBF:goto(200)
oDBF:save()

James

Rao,

For TDatabase, lBuffer is .t. by default.

Yes, I understand that. But if you change something like that it is wise to save and restore it's state. It is wise to do as you suggested, set it to true at the start of the routine because you can't depend on it being true already.

As I expect you ...

For TDatabase, lBuffer is .t. by default.

Yes, acopy() would be faster. If you set oArqCli:lBuffer I also suggest saving and restoring its state so as to prevent any possible problems elsewhere.

James

Local lBuffer ... lBuffer:= oArqCli:lBuffer oArqCli:lBuffer := .t. // this is default oArqCli:GoTop() do while ! oArqCli:Eof&#40 ...

... DbSkipper

//----------------------------------------------------------------------------//

CLASS TDb

DATA nArea AS NUMERIC INIT 0
DATA lBuffer
DATA lShared AS LOGICAL INIT .t.
DATA aBuffer
DATA bBoF, bEoF, bNetError AS CODEBLOCK
DATA cAlias, cFile, cDriver AS String INIT ""
DATA ...

... the database object mainly because the object is loading the buffer array with all the fields. It is also checking for the BOF or EOF. If you set lBuffer:=.f. it will be faster. See database.prg - the skip() method.

The database class will always be slightly slower, but not much. Your example is ...

... FieldGet( n ) ) read a record which does not exist in the database yet.
Best regards,
Otto


METHOD Modified() CLASS TDataBase

local n

if ::lBuffer
for n := 1 to ( ::nArea )->( FCount() )
if ! ( ::cAlias )->( FieldGet( n ) ) == ::aBuffer[ n ]
return .t.
endif
next
endif

return .f.