I posted a while back about being unable to unprotect a shared workbook to erase it's change history and then reprotect it through VBA, even though the same sequence can be done manually.
To get round this, I set the period for changes to be kept to 32 days and wrote a small routine for our QA dept to extract (copy and paste) the change history to a separate workbook once a month.
The problem is, changes over 32 days old are still present in the change history list. The way I thought it would work is that changes would be kept up to 32 days and then sort of 'drop off' and so only a 32 day rolling period would be there, and the workbooks wouldn't 'bloat' over time. Can anyone explain why they're still there?
As a sidenote, I used the PurgeChangeHistoryNow method to try and delete changes, the workbook actually ended up bigger in size than before(!). I hate shared workbooks
.
This message was edited by Mudface on 2002-05-07 01:58
To get round this, I set the period for changes to be kept to 32 days and wrote a small routine for our QA dept to extract (copy and paste) the change history to a separate workbook once a month.
The problem is, changes over 32 days old are still present in the change history list. The way I thought it would work is that changes would be kept up to 32 days and then sort of 'drop off' and so only a 32 day rolling period would be there, and the workbooks wouldn't 'bloat' over time. Can anyone explain why they're still there?
As a sidenote, I used the PurgeChangeHistoryNow method to try and delete changes, the workbook actually ended up bigger in size than before(!). I hate shared workbooks
.This message was edited by Mudface on 2002-05-07 01:58
