We have a practice of saving a copy of our project plan with the status date in the filename every time we update status. This messes up the shared resource pool, because the resource pool now thinks that the updated file is ANOTHER project.
The workaround is to open the older version, remove the shared resource, and edit the resource pool and break the link to the older version(s). But this seems tedious and overly manual.
Is there a technique on the resource pool / save a copy side that can deactivate the older versions of the project, or tag two versions of the project as actually being the same project?
Or is our approach of saving backups of our project plans the incorrect workflow, and if so, what do you recommend as a safeguard against project corruption or user entry error?