PowerInroads SS4
I am sure this question has been asked many times and I have read a few of the posts on how to resolve the xin read-only prompt but I want the xin file set as read-only since the file is the organization standard company wide. So the question is, does a configuration variable exist that will suppress the read-only prompt. In the event that a project needs to edit the xin file, then it would be copied into the project structure where it is editable. So far I am unable to find a way to suppress his without a coded solution or moving the file to a editable location as noted above.
You might be able to trick it. When on a share, the XIN uses an LCK file to manage who has the file open for read/write. If you copy the lck file while it is checked out by say, an administrator, and after the free it, you replace the lck file, anyone opening the XIN should see that its read only by the admin. As long as the admin never opens the xin again, the LCK file should keep it locked by the admin. You might need to make the LCK file read only, but I am not sure.
In this situation, I would teach users to make their own XIN by copying the locked one and when they open their XIN, even if it is in a project share, it will get its own LCK file that multiple users can use to control read write access for the project XIN.
The reason I think this might work is that I have seen instances when an LCK file was inadvertently left in place and a user was known not to be in any product and it kept the file read only for everyone until we manually deleted the LCK file.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration Maryland DOT - State Highway Administration User Communities Page
thanks for the information. I will test it but not sure I will deploy that as a solution. Is probably easier to place the file in the project. Luckily, so far I have not seen this issue in OpenRoads CE. Thanks again!
While Open Roads no longer uses an XIN, it still uses ITL files. These are not write locked when one person opens it and since it is pointed two by a variable, it is very likely that two persons on a project will open the same ITL at the same time. The one to save theirs last wins. Unless you make them read only, but I've never had a project where all of the templates were ready to use without modifications. Even when I had created entire folders of jurisdictional typical sections for a land development company, there were always reasons to modify a template here or there.
And this issue existed in the InRoads world - this is not a new problem in ORD.
thanks for the info! I appreciate it.