Michael,

At one time I supported a group that had this requirement, no multiple edits (much like the way they had SourceUnsafe configured). As you've found with Perforce multiple, simultaneous edits is always on. The only way we thought about overcoming the problem was to assign owners to specific files via p4 protect. This is really not that great when you consider your source hierarchy may be in the multiple thousands of files range and it is structured such that no-one has ownership of any one area. If you had only a few specific binary files then it might be OK to have them writable by one person (or a very small group that communicated amongst themselves very well).

What I ended up doing was instructing all of the users to lock the file on check-out. More of a process then anything and this could be wrapped in a check-out script so they wouldn't forget to do it.

Todd