>However, you have to be aware of users who leave an editing screen open when they leave for vacation, edit/read-only has to be VERY carefully controlled, etc. We have a program where the same record may be shown in 15 different forms in various ways. We went with optimistic buffering because we rarely have editing conflicts, but the users want the option to edit available without and >EDIT button.


Also , it is not that difficult to program conflic management
and IAC, you only have to do it once in a class and that's it
We for example use views and optimistic buffering (record and table)
and it is set up so that 2 people can edit the same record one changing the phone number and one changing the address - and have both changes get registered.

Arnon