(Home) Most-Recently Used (MRU) , What is Most-Recently Used? ; AutoSave and AuditSave , The Environment , Triggers , File Save Actions , File Close Actions , What About Third-Party Triggers? , Slave Functions , What about MRUse? , FileSaveAll, FileCloseAll, FileExit , The Set Of Procedures , lSaveAs , lClose , lFolderExists , lFileExists , lFileOverwrite , mFileSave , mFileSaveAs , mFileClose , FileSave , FileClose , FileSaveAs , FileSaveAll , FileCloseAll , DocumentClose , FileExit ,

File Close Actions

On this page we will outline the actions to be taken for each of the eight possible combinations when the user issues a File Close command on a document.

Notes

(1) In general such a solicitation can result in a tri-way response of Yes/No/Cancel, and the Cancel result is of great interest in situations such as File CloseAll or File Exit. If the user responds “yes”, then we go ahead and try to save changes. If the user responds “No” we do not save the file, but close it. If the user responds “Cancel” we do not save the file, we do not close the file; we abandon all processing and return control to the user immediately.

(2) The problem here is that “save changes” will not be showing the original file name, that having been superseded by the audit file name.

(3) The logic here differs from that for File Save. File Save is an interval in the use of an open document; user-processing can continue after the File save trigger is completed, but File Close terminates the existenc eof the open document. If the document is not dirt, what is to be gained by making an Audit Copy? Or should the same rules apply as for File Save?

In all eight cases our aim is to reduce the triggers to that of the equivalent File Save if the user has elected to save changes, and then complete the trigger with a standard close-without-saving-changes.

File Save Actions

What About Third-Party Triggers?

Search