(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 ,

AutoSave and AuditSave

AutoSave

Microsoft Word Autosave (Tools, Options, Save, “Save auto recover information”) does not save a spare copy of the document(s).

I decided to write some code that would make use of the nominated time interval to effect an interim save of the active document, or of all open documents.

Audit Save

Microsoft does not provide a means of developing an audit trail of my work.

I decided to write code which would use the time interval in “Save auto recover information” to drop a time-stamped copy of the active document in a nominated folder.

Third-Party Triggers

While I was at it, I decided to make this code available to any 3rd-party package whose designer was aware of the MRUse application.

A simple example: I have a package Under-The-Hood (“Under”) which includes some file saving mechinsms. Under can interrogate its environment to see if MRUse exists, and if it does, can effect its file-saving throyugh MRUse’s procedures to take advantage of Audit trails and so on.

The Environment

Search