Hi Nick,Sorry for the late reply.Currently when someone is editing a particular visit /invoice  (anything) we don't "lock" the record and then if someone else tries to edit it tell them it is in use.  The protection against over writing someone else's changes is when you save the record where it will reject the changes if the system notices the information has changed since you started editing it.    Essentially the first person to save the information wins approach. To be honest we decided to use this approach as it was easiest to implement and we had no evidence that it was a major issue although we definitely recognise  when it does happen it is painful.  One alternative is to lock the record on edit but this has it's own issues.  Specifically someone can leave an editing screen up or just close a browser or disconnect their PC/workstation and that will effectively block everyone out of the information.  This has been an issue with a number of software packages and generally means someone has to run around and find the screen editing the information and cancel it in order to enter information on a customer or patient. Not an ideal solution. The alternative we have considered is if a conflict is found try and merge the two versions of the information.  May be tricky depending on the nature of the changes i.e changing the same notes in a visit versus adding different medical record entries. A common alternative with web applications is to maintain some kind of locking mechanism that times out.  Again possible but would require a reasonable amount of development.While we ponder and decide on the best approach there may be some things you can do to limit the occurrence of the issue.  Firstly it would good to identify the scenarions that are most likely to cause the issue.  I.e under what circumstances two people edit the same visit.  Maybe some procedural changes may minimise the issue.  If you could relay this information back to us it will help us design a solution that has minimal impact on the rest of the application. What may also help is to make sure you use Apply to save the information as you editing so you limit the impact of a potential lock.  Habitually hit Apply if for any reason you need to leave the workstation and are in the process of editing an invoice or visit. The development team will work on a more permanent solution :-)CheersTony  On Wed, Oct 28, 2009 at 9:42 AM, <paradisevets@internode.on.net> wrote:

Not infrequently we get the annoying error where someone has just entered the patient history(notes) after a consult and on apply/ok the whole lot is deleted because 'the file may be in use by another user'. Is it possible to prevent this from happening - either a warning or total lock out of editing by a second user?

Cheers, Nick _______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: //lists.openvpms.org/listinfo/users" target="_blank">http://lists.openvpms.org/listinfo/users Posts from this mailing list can be viewed online and replied to in the OpenVPMS User's forum- //tinyurl.com/openvfu" target="_blank">http://tinyurl.com/openvfu

-- ______________________________________________________________________Principal ConsultantVertical Connect Pty LtdPhone :  +61 (0) 3 97229824Mobile:  +61 (0) 4 21347105 Email   :  tony@verticalconnect.netWeb    :  //www.verticalconnect.net">http://www.verticalconnect.net