T
tbone
I'm familiar with Excel 2003 VBA, and I'm starting to apply some of my
logic to Project 2003.
In Excel, I use SaveCopyAs in the Workbook Open event to create a
backup copy once per day with the date included in the filename. This
allows a backup trail if needed, and the logic purges after so many
backup files.
SaveCopyAs provides a way to save the current workbook to a file with
a different name while leaving the name unchanged in the current
workbook. I don't see a similar functionality in Project.
I kludged around it by reopening the original project file after doing
a FileSave, then closing the (renamed) backup file right in the Open
event after purging old backups. The reloaded project now sees that a
backup was already done today, so it exits the Open event routine. The
only problem with this is that I get the macro security warning twice.
Alternatives enthusiastically entertained.
Thanks
tbone
logic to Project 2003.
In Excel, I use SaveCopyAs in the Workbook Open event to create a
backup copy once per day with the date included in the filename. This
allows a backup trail if needed, and the logic purges after so many
backup files.
SaveCopyAs provides a way to save the current workbook to a file with
a different name while leaving the name unchanged in the current
workbook. I don't see a similar functionality in Project.
I kludged around it by reopening the original project file after doing
a FileSave, then closing the (renamed) backup file right in the Open
event after purging old backups. The reloaded project now sees that a
backup was already done today, so it exits the Open event routine. The
only problem with this is that I get the macro security warning twice.
Alternatives enthusiastically entertained.
Thanks
tbone