From: Baskaran Subramaniam

Here is a new problem.

I have figured out how to deal with submit/resolve/merge/submit cycle whenever there is a conflict. This works fine for standard text files. However, I am trying to figure out the procedure for dealing with codewarrior project files. These project files are binary (they don't use the Mac resource fork though), How do the MacOS users of Perforce deal with resolving conflicts?

BTW, is there any way I can tell Perforce not to allow more than one client open a file for edit? That will help us until we figure out how to deal with resolving binary files.

Thanks a lot.

Baskaran Eastman Kodak