The information in this article applies to:
When I try to open a particular file, this message displays:
"The file appears to be locked. This could be the result of another user or program using the file. This may also result from having insufficient security privileges to access this file."
What do I need to do to open this file?
Just as this warning message indicates, there are a couple of broad reasons why this may occur:
The best way to resolve this issue will depend on the cause.
There are several scenarios in which a Chief Architect plan or layout file that you wish to open might already be in use elsewhere. It could, for example, be:
The first of these scenarios is easy to resolve - if another version of Chief Architect is running, simply save your work and close the file.
The second scenario requires a little bit of investigation. Save your work and then close your Chief Architect or Home Designer software.
For Microsoft Windows:
For Mac OS X:
The third scenario means that the file may stored in a shared location on this computer or on another system that is connected to your local area network and the file is being used or edited by another process on that system.
Working on files from a shared directory or external location is known to cause problems such as slow performance, file corruption due to data loss, or changes not being saved.
As a best practice, we recommend copying the projects to an unshared location on your local computer while working on them. Then copy them back once you've saved your work and closed your Chief Architect or Home Designer program.
If the file is locked because another user on the same network has it open on their system, then you can have them close the file so that you can open it. If it is locked and does not appear to be in use on any other systems, restart all the computers that are connected to the network and try opening it again.
If you are sure that the plan or layout file is not already in use elsewhere, then it is likely that your user account for this system does not have sufficient rights to access the file where it is currently saved.
One way to avoid this issue is to have the user that created the file(s) copy them to a location that you have access to, for example the Public user's Documents directory.