|
Do not lock a record til you are ready to update it. Otherwise users will hunt you down and explain things to you. Then their bosses will hunt you down and explain things to you. Then your boss will hunt you down and explain things to you. The easiest way I've found is that when I originally write the subfile record I include a hidden field which is a complete copy of the fields I care about (or the whole record). When I process the subfile for changes I process one record at a time. The first thing I do is to compare the current version of the record with the original version in the hidden field. If they are identical I continue processing the record. If they are different then another user has already changed the record at another work station. Knowing the record is already changed in some way alerts you to a potential corruption of data. How you deal with that is another matter, but at least you know. Locking lots of records is not a solution that will win you praise though. --------------------------------------------------------- Booth Martin http://www.MartinVT.com Booth@MartinVT.com --------------------------------------------------------- -------Original Message------- From: rpg400-l@midrange.com Date: Monday, October 14, 2002 02:19:28 PM To: rpg400-l@midrange.com Subject: update in single page subfile Hi I want to update records in subfile which is having thousands records(lessthan 10k)..(reading this records is done in single page)...please suggest me which subfile is good (loadall/expand/single page)to update and at the same time i should lock the records without giving chance to others to update...how can i lock the records? best Regards Murali
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.