Problem resaving Prism .pzf or .pzfx files after making changes

This is a rare problem that has to do with file permissons.

First some background. Saving a new file is just that --- saving a file. However, resaving a file is much more complicated. To avoid deleting the existing file until the new file is saved, Prism follows these steps:

1. Save the current project as a temporary file. Prism Windows uses a .pz$ or .pzf$ extension. Prism Mac uses a .pzf$  or .pzfx$ extension.
2. Delete the prior saved verions of the file.
3. Rename the temporary file with a .pzf or .pzfx extension.

Resaving requires Prism to save, then delete, and then rename a file. These steps can require different permissions. It is quite rare for this to be a problem, and the problem almost always occurs with nonstandard networks. So ask your network administrator to help fix file permissions.

Before Prism 7.0a Mac and 7.04 Windows, Prism managed this process itself. Starting with Prism 7.0a Mac and 7.04 Windows, Prism relies on MacOS or Windows to handle the saving, deleting and renaming. If you have had problems, they probably will go away if you update. 

We know of one unusual situation that will provoke a message in Prism 5 Mac. If you try to resave a file using the File Save As dialog, you'll see the misleading message, "Cannot save document. This file is being used. Save it under a new name or another location." There is no need, of course, to use File.. Save as to resave a file using the current file name. Simply click Save or use the File..Save command. File... Save as works fine for its purpose of saving a file with a new name or to a new location. The misleading message occurs only when you try to use File.. Save As to save back to the same location with the same name.