FiveTech Software tech support forums

... file lock. It would be beneficial, especially considering mod harbour, to have a standardized function: buffer and then check before saving if the buffered data is still current. Best regards, Otto

Perhaps I found a solution I used oDbf:load() because There is no Method locate() in TDatabase and locate is not buffered Function Locate_Records3(anno1,anno2,oDbf) local aLocate:= {} LOCAL nFirst,nLast oDbf:use() select(oDbf:nArea ) oDbf:gotop() locate for year(FIELD->data) ...

Silvio, Here is an example. This is fully network compatible. Open a file object with one line of code. Databases are open in shared mode, buffered, optimistic locking, no dealing with aliases workareas, etc. Use this with the customer.dbf file you recently sent me and/or change it slightly ...

... presume this is a network mulit-user application ? 2) If Yes, does this application have a lot of transactions that may change quickly and make a buffered up oRs on a client machine stale ? Generally speaking .. I like the Local Cache parameter because the fetched cursor ( data to be browsed ) ...

... object represents a single customer. It is independent of the table. It has its own data which is copied from the customers table. It is thus buffered and is only saved when (and if) you, or it, call(s) the Save Method of the customer object. The only time you would have to call it is during ...

... performance. I have provided both options (1) switching indexes and (2) setting filter. We can also compare the response times. Note: TDatabase in buffered mode slows down browsing speeds consderably. It is better to use non-buffered mode and the best option is to browse DBF directly. #include ...

... the problem was in my code? I dont' know, but I know that you should not make "premature optimization". We don't need a general tool for buffered write. We need to clear understand if and where the problem is. EMG

... the array(400), less problems too. What about to create a TBufferedWrite class? Initialized with the File Handle and the minimun size of buffered input, a Write( cString ) method, and an End() that writes the remaining not written bytes.

... ( 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 suggest you do not do anything. Just use it. You can work directly with RDD too. The above sample code works directly with RDD also. Why ...

... the database especially if the database is on a network share or client\server so database corruption ( especially Ms Access ) is not that common. Buffered variables ( add and edit ) are not written to the table until oRs:Update() so if the box crashes or the network 'hick-ups' .. the variables ...

... I suggest in the next example. 2) As far as a DELETE that occurred from Workstation B .. Workstation A's visibility will not see any change in its buffered rows, hence your run-time error .. what you might consider is modifying my above example like this and if the Try\Catch errors .. you can either ...

Antonio Linares wrote:Enrico,

If a buffered chunk of data is written and part of it gets corrupted, that could do it

Then you would get a corrupted record not a vanished record.

EMG

Enrico,

If a buffered chunk of data is written and part of it gets corrupted, that could do it

A log file (what I named a "backup" dbf) could reveal if the operation was done but the record vanished (?). I am just guessing, trying to imagine what may be going on...

... with their detail and the application was very stable. Obviously I had to go back and re-write my table visibility because all my records are buffered up when the Master property screen comes up .. which presented a challenge of forcing requery() .. I decided there had to be some crazy reason ...

... thru the master\detail as many times as I wish .. However, now I am dealing with rewriting the concurrency and workstation visibility with stale buffered up recordsets. I did not have to deal with that because I was always opening up a fresh recordset with each time I looked at the detail. Within ...