FiveTech Software tech support forums

I just tested a database of 26,000 records. With, or without, buffering it is quite fast--about 1 full screen per second (on a local drive). If yours is slower, it is due to other routines you are calling from TXBrowse, not TXBrowse itself. I'm not sure ...

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 ...

Turn off buffering.

oDBF:lBuffer:=.f.

... possible. The philosophy was to write each piece of code only once. So, in this case, it handles all scatter and gather routines, record locking, buffering, loading and saving the data all done with multi-user compatiability. It has worked great with every other customer I have had except you ...

Great !!!
Can it be used for buffering the write on DBF files too ?

... I resolved the first problem keeping a HGLOBAL with the gif from resource, so loading it in memory. The second problem is solved using double buffering and the background brush. Because is a little big, i put the code online: http://amicoperry.altervista.org/data/gif.prg It ...

No es exactamente el mismo caso, pero alguna vez utilicé una técnica de buffering con browses con muchas columnas, y esas columnas eran cálculos más o menos complejos hechos de forma dinámica.
Tendría que ver exactamente en qué consistía.

... read and understand. What you don't see is all the code it inherits. You don't have to deal with workareas, opening databases, alias referencing, buffering data, record locking and record locking failures, etc. James James, I'm not ready yet for this.... I'm in a copy/paste from samples and build ...

... read and understand. What you don't see is all the code it inherits. You don't have to deal with workareas, opening databases, alias referencing, buffering data, record locking and record locking failures, etc. James

Hi Enrico, We need to clear understand if and where the problem is. IMHO the "where" is clear: buffering in a string built of small pieces in a intense computing program could lead in reallocation problems due to Harbour's memory management lack of garbage collection. ...

... after each record during APPENDs. This was taking 11 hours to append 26 thousand records. Appending the same file using DBFs took 1 second. So, buffering before writing to disk provides a tremendous increase in speed. One would expect this since writing to disk is a physical process which will ...

... level buffer. The only time it would stay at a lower level buffer is if the system is too busy to process the input in time. At this level 'buffering' is really just a semantic concept; the system is basically at rest, the input has been processed, transformed into a UTF-8 string and stored ...

... level buffer. The only time it would stay at a lower level buffer is if the system is too busy to process the input in time. At this level 'buffering' is really just a semantic concept; the system is basically at rest, the input has been processed, transformed into a UTF-8 string and stored ...

... with my enhanced TData class. For more info about database classes, TData, and TRecord see my website gointellitech.com. [Yes, this is double-buffering, but made simple and smart.] oItem:= TRecord():new(::oItems) oItem:qty:= 7 oItem:save() FWH natively provides TDataRow() oRec := TDataRow():New( ...

... data without it affecting the database record. So, when you are then assigning the oTdesc:desc1 data to a memory var you are essentially double buffering the data (and writing way more code). So you can now do: oDesc:= TDescrip():New() oDesc:desc1:="whatever" oDesc:save() And you have ...