Can test plans/cases/scripts be opened in read-only mode ??

Hi all,
I have a severe problem; If 2 persons edit the same test plan/case/script at the same time and person A then saves the work, all changes made by person B will be lost when B tries to save his/hers work - person B been giving the message that the version you have open is not current, and that all will be lost.
Can you, and if yes, how, control this ? can you set up to have "read only mode" as known in for instance Word and Excel ??
I have a severe problem; If 2 persons edit the same test plan/case/script at the same time and person A then saves the work, all changes made by person B will be lost when B tries to save his/hers work - person B been giving the message that the version you have open is not current, and that all will be lost.
Can you, and if yes, how, control this ? can you set up to have "read only mode" as known in for instance Word and Excel ??
One answer

There are two concepts that might help here.
The first is to lock assets when they should not be edited.
See this doc that describes "lock" at the end. http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/topic/com.ibm.rational.test.qm.doc/topics/t_create_testplan.html
Another approach is to customize permissions so that some user groups do not have the permission to edit test assets.
Relevant doc:
http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/topic/com.ibm.rational.test.qm.doc/topics/c_permissions.html
http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/topic/com.ibm.rational.test.qm.doc/topics/t_mod_permissions.html
http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/topic/com.ibm.rational.test.qm.doc/topics/c_permissions_reference.html
A simple "merge" capability when asset saves collide is a feature the team has been thinking about for a while now and may show up in a future release.
The first is to lock assets when they should not be edited.
See this doc that describes "lock" at the end. http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/topic/com.ibm.rational.test.qm.doc/topics/t_create_testplan.html
Another approach is to customize permissions so that some user groups do not have the permission to edit test assets.
Relevant doc:
http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/topic/com.ibm.rational.test.qm.doc/topics/c_permissions.html
http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/topic/com.ibm.rational.test.qm.doc/topics/t_mod_permissions.html
http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/topic/com.ibm.rational.test.qm.doc/topics/c_permissions_reference.html
A simple "merge" capability when asset saves collide is a feature the team has been thinking about for a while now and may show up in a future release.