The AccuTerm forum has moved. Go to community.rocketsoftware.com to register for the new Rocket forum. |
WED read-only mode |
Post Reply |
Author | |
Auctor
Newbie Joined: February 28 2017 Status: Offline Points: 16 |
Post Options
Thanks(0)
Posted: January 04 2018 at 10:28am |
I'm curious about the philosophy of WED "read-only" mode. The main reason that I would use read-only mode is to look at a record without interfering with other processes that may need to read and possibly update that record.
However, I have discovered that WED always issues a READU lock when it reads a record, even if has been told to open a read-only copy. Is there a reason for locking a record that WED does not allow the user to update? |
|
PSchellenbach
Admin Group Moderator Joined: December 15 2003 Location: United States Status: Offline Points: 2150 |
Post Options
Thanks(0)
|
Hi Auctor -
Looks like a contradiction in how wED is implemented. The READU happens because the option to use record locking in wED is enabled. It does make sense that read-only would override the locking option, but they are being handled independently. So wED opens the locked record in read-only mode. If another process had locked the record, wED would probably complain, but open the record after confirming to open in read-only mode. Thanks, Pete |
|
Auctor
Newbie Joined: February 28 2017 Status: Offline Points: 16 |
Post Options
Thanks(0)
|
Is there any way to customize that behavior or is it just the way that ATWED32.EXE is coded? I tried setting KMTCFG field 58 to 1 but it made no difference.
|
|
Post Reply | |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |