Document Locking and Unlocking

I have a Notes Db that was original written on a Notes 5.x client. Within this Db, they wrote custom code to lock and unlock individual documents.

Over the years, I’ve had to go into this Db and make minor changes to the form layout, add/changes view, etc., but have never touched the code related to locking and unlocking.

Since being on Notes 8, I’ve made cosmetic changes to the forms, but never to the lock/unlock code.

Within in the last 6 months or so, we’ve had an increasely large number of problems with documents in this database remaining locked.

My question is. . . with Notes 8, is it necessary to have custom code on a form to handle locking and unlock of individual documents? Or could most of that code be striped out and agents be created to “Lock” and “Unlock” documents using the simple @ functions available since Notes 6.5?

Subject: ECADS?

It seems likely that you could use the built-in functions instead, but without knowing what else the code in question might be doing besides controlling locking, it’s hard to say. E.g. does it also handle versioning documents?

Subject: Custom Doc Lock Code

No versioning code is involved. it is LotusScript code that basically checks if a doc is locked, sets the lock, and removes the lock.

Do the built in locking functions prohibit the user from editing a document that is locked by some else? Or does it allow the editing then warn the user when they try to save their changes that someone else has the doc locked?

Where can I get some good detailed information on the built in locking functions and maybe some “real world” examples of how these functions work?