FiveTech Software tech support forums

... I fire off a separate recordset back to the master table looking just for the primary key ( row id ) and the "updated" field .. if the buffered up record has the same value as the the table .. I commit the record .. if the master table has a greater value than the buffered 'updated' ...

... deleted a row and I tried to trap the second app from trying to delete the same row since to app 2 his recordset still had the 'deleted' record buffered and displayed. What I did was in the delete routine .. I stored the unique row id of the record to be deleted .. did a oRs:Requery() to refresh ...

Hi Rimintas, Again a database object is going to be a good answer. It is automatically buffered. However, it is difficult to do spreadsheet style editing with cell level validation and control. Also, how does one trigger the save? On a cell by cell basis or only when ...

Hi Rimintas, Again a database object is going to be a good answer. It is automatically buffered. However, it is difficult to do spreadsheet style editing with cell level validation and control. Also, how does one trigger the save? On a cell by cell basis or only when ...

... I don't have a direct answer for you .. but consider a couple options .. 1) In a network environment you could have issues with two people having buffered up the same record .. very typical in a small office situation .. if one person saves the record and the other saves on top of that same record ...

For James and Antonio,

Database class

I am using TDATA now with the new database class fom version 9.02.

Testing the length of a buffered field ( N,3.0) now returns 10 but the field is only 3.

If I link in the old database.prg the values are correct.

Regards,
Otto

... the buffer, cancelling the changes made to the buffer (Equivalent to calling :Load() ) 14) Modified(): Returns .t. only when :lBuffer is true and buffered values are different from the dbf field values 15) New Method: Updated(): Returns .t. when either Modified() is true or any dbf fields are ...

... On the Falcon 4420 it works very well and long complex EAN128 barcodes can be scanned, decoded and parsed at 2 per second! Because the scanner is buffered, none are ever lost but just wait in the queue. I also tried the standard 'keyboard wedge' function but found it to be so slow as to be totally ...

... ) // returns James And then you can change the data in the name var: oPatientList:name:= "Doug" msgInfo( oPatientList:name ) // returns Doug This buffered data, the disk record still contains "James" until you do a save(). So you can use these in controls and if the user selects OK you do a oPatientList:save() ...

... bOnRowLeave: If specified, this user specified codeblock is evaluated before leaving a row, if Data oBrw:lEdit is True. This is useful in case of buffered writes of entire row as in TDataBase or similar classes or for committing after checking the validity of entire rows. When SetADO or SetODbf ...

... it all done automatically without any programming far outweighs any tiny speed gain if it actually exists. Remember that disk reads and writes are buffered so there may not be any speed gain. Additionally, reading and writing only certain fields means that you have to have different load and save ...

James Bott wrote:Detlef,

Aren't you using TData? Did you know that the data is already buffered?

In TData the fieldnames are stored in aFldnames.

Perhaps if you explain what you are trying to do, I can help with a TData solution.

James

Where is Tdata class?

Thanks,
Carlos G.

Detlef,

Aren't you using TData? Did you know that the data is already buffered?

In TData the fieldnames are stored in aFldnames.

Perhaps if you explain what you are trying to do, I can help with a TData solution.

James