posted 20 years ago
Hi Badari,
Yes, there have been people who have done it and passed.
My personal view is that this is not correct from an extensibility viewpoint. Today we need to lock one record, modify it, and unlock it. Tomorrow the requirement may change where we need to lock two records, modify both, and unlock both. If we cant do the modification on one then we cannot do the modificaton on another. If you have the lock done behind the scenes, then when it comes time to extend the project, the locking code has to be removed from the class you put it in, and moved to the class handling two simultaneous modifications.
Regards, Andrew