>> >> >>>>>>>You should make a choice: if you use RLOCK() then you don't need in buffering at all. >>>>>> >>>>>>I wouldn't say that Ed. You still need buffering to use TABLEUPDATE() and TABLEREVERT(). >>>>> >>>>>If you use RLOCK(), then you need in neither buffering nor tableupdate/revert. If record is locked by you, then nobody else will change it, right? So, what helpful information you may get from buffer? >>>> >>>>You still need buffering to allow the user to save TABLEUPDATE() or discard TABLEREVERT() the additions/modifications to data. >>> >>>No, as long as I use unbound controls. >> >>True, however your statement "if you use RLOCK() then you don't need in buffering at all." is incorrect. Using unbound controls is eliminating the need for buffering but this has nothing to do with using or not using RLOCK(). >> >>When using databound controls you have to use buffering to use TABLEUPDATE()/TABLEREVERT(). RLOCK() has nothing to do with this either. > >"Using RLOCK() and unbound controls, you don't need in buffering at all." Is it Ok now?
Look Ed, I'm not trying to have a confrontation, in fact, I personally value your opinion and have received great advise and help from you. . I was just clarifying a statement, for the benefit of the original poster of this thread, that *as worded* was incorrect.
Cheers
Colin Magee Team Leader, Systems Development Metroland Media Group Ltd. Mississauga, Ontario, Canada
