Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Form Not Releasing Lock

Status
Not open for further replies.

Earthworks

IS-IT--Management
Sep 30, 2003
16
GB
I have a form that randomly does not release the edit lock and have had to code an unlock button for users to get around the issue until resolved.

All clients are the same version 6.5.1 and accessing the db from a Citrix session. I have investigated every possible cause with no success.

Is it because they are testing while I am developing at the same time on the same copy, and this could be causing an issue?

Anyone had same/similar issue and resolved it?

 
Are you testing locally or are you using a server to host the database ?

It is highly recommended to do development on a server - the client does not have the same reliability - especially concerning document locking.

Incidentally, what method do you use to lock documents ?

Pascal.


I've got nothing to hide, and I'd very much like to keep that away from prying eyes.
 
Thanks for your reply.

The database is on a server.

I'm using the Database -> Properties -> Allow Document Locking and nothing else.

Think I may have to turn this off and when a user attempts edit mode check if it is already in edit mode and not allow them to go into edit mode if another user is editing.

No locking required?
 
So you are using Notes locking. I am sorry to say that Lotus is not exactly stellar on this. My Notes development experience now spans 12 years, and I have not met many developers who trust the server on this point.

Meaning to say that most devs I know have implemented their own locking solution. Said solution is always a variant of the following :

If doc opened in edit mode :
- use the QueryOpen event to check a view for the UNID of the document
- if UNID not in view, create lock doc with UNID
- if UNID already in view, block user from opening in edit mode
- check again in QueryModeChange - to trap the case where a doc is opened in read mode then user edits it
- in the QueryClose event, if edit mode was allowed, check the view again to mark the lock doc for removal, bumping it from the view


That it basically how I've been doing doc locks for years now, and many people I know do around the same thing.

The Lotus-standard database option is not reliable enough.

Pascal.


I've got nothing to hide, and I'd very much like to keep that away from prying eyes.
 
Ok - as I have only a few months experience, I will lose the Notes locking and implement your suggestions as the system with the locking issue, is not useable and does not help instil user confidence.

Thanks
 
If you need help for implementing this, just reply here and I'll give a hand.

Good luck !

Pascal.


I've got nothing to hide, and I'd very much like to keep that away from prying eyes.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top