... this type of resource would no longer be necessary, however there is still a lot to be done on the web. The program has many modules. Let's stay optimistic thanks to mod_harbour.
... to do this. 2) How to run an Rlock or Flock to prevent two users from working on the same record or groups of records. We can open a table with optimistic locking or pessimistic locking. Mostly tables are opened with optimistic locking and there is no need to locking. If we open a table with ...
There are two methods of file locking, optimistic and pessimistic. With optimistic, the user loads and edits the file, then when they are done, the record is locked, saved, and unlocked. With pessimistic, the record is locked, the user edits ...
... 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 to work ...
... := .F. # endif Shows only a window "Attention" , then the aplication freezes . "2048 The record was not saved because optimistic concurrency was in use." doesn't appear anymore I tried also to set locktype to adLockPessimistic ( in adordd , oRecordSet:Open( ....,2,...) ...
... 4) Use fieldput() in bonpostedit BUT It is still impossible to change the value from a logical field : "2048 The record was not saved because optimistic concurrency was in use.",; It seems only the case on logical fields , other fields can be modified. Any sugestions ? Frank
What I do is not probably relevant. Optimistic locking or batch optimistic locking or detached recordsets, depending on the situations, but never lock and wait for user-input. Even ADS by default uses optimistic locking. Option of Pessimistic ...
... many enhancements. I added some enhancements for record locking including automatic retries if a record is already locked. Personally, I aways use optimistic locking so a record is only locked for a second, so locked records are not really an issue. I rarely use file locking and I have not really ...
... on locking / updating issues with databases in a multi-user setting. Do you deal with any of that with your new recordset ? Mostly we work with optimistic locking. This is automatic. You must be knowing about it in ADS. We can also use pessimistic locking like in our traditional dbf, but nobody ...
... of the 3rd party programs have built in features for SQL ( like Codejock ) that simplify the usage, but not for DBF. As I look to the future ( optimistic for this old timer ), I know I should make the transition. Remote desktop may work for you, but I don't see a need for it in my case. Finally, ...
... finding it out. In line 355, please change ::AddNew() as oRs:AddNew() Next question about multiiuser issues: 1. If recordset is opened with adLockOptimistic: If other user modified the same record we get a runtime error when we call oRs:Update. So catch the error in TRY/CATCH block and dealwith ...
... with his own codeblocks. XBrowse internally implements locking and unlocking where necessary. For ADO most common locking system adopted is Optimistic Locking and it does not require placing explicit locks. testxbr3.prg shows usage of reports also. Also please see xbincflt.prg in samples
... face the possibility of another committing a change in that minute fraction of a second unless pessimistic locking is used and row is locked. With optimistic locking, finally we need to attempt write and handle the failure finally in some way or other. Even if the probability is very low, our code ...
... This also allows you to lock and update multiple records at one time (multiple records are locked, then updated, then unlocked). If you use optimistic locking the record is locked, saved, and immediately unlocked during the save method. Regards, James