BeforeSave .Save / .SaveAs events not triggering when triggered by macro

Hi,

Bit of a strange one this.

I have two workbooks, one a Tracker which houses the majority of data and code and the other a Timeline which is largely controlled by the Tracker but also has some small amount of code.

The Timeline has some code in the BeforeSave event which prevents the user from using SaveAs, backs the file up to an alternate location, etc. When I click on save whilst in the time line the code runs perfectly. However when I initially set up the Timeline using code housed in the tracker the save fails - with no error.
The .save line in the Tracker triggers the Timeline's BeforeSave but when it goes over each line of code to save and create the backup, nothing happens. I've tried running it with DisplayAlerts and EnableEvents set to true - just to see if any error message shows - but nothing. Perplexed.

Tracker:

Please Login or Register  to view this content.

Timeline:

Please Login or Register  to view this content.

Any ideas why the BeforeSave code would run fine when triggered by the user (e.g. File > Save) but not when triggered from another Macro?

Any help appreciated - as always, TC.

Hi Norie,

The Error handler isn't triggered but I have annotated it out and run the code again - exactly the same thing happens. Each line of code is stepped through as if all it working okay, no errors - but nothing actually happens, the file isn't saved.

Confused.

Please Login or Register  to view this content.

The first line will in effect respond to any dialog with its default response. The default response to the message raised by trying to save onto an existing file is 'Do not save'.

Thanks for this. Okay, I think I get what you're saying. I didn't realise the default was not to save. It also overwrites fine when the code is prompted from the user clicking on save. Strange.

How can I force it to overwrite - do I need to use ConflictResolution, though this reads more like it's to do with shared file conflicts rather than overwriting...

I've had a google but can't see anything specific

Why do you need SaveAs instead of Save?

It seems I have been incorrect - in this instance the default option is not effected.

I need to saveas to remove the password protection on the file - so I can then savecopyas to an alternative location - then reinstate the password, allowing the user to maintain control of the same itteration of the file. Basically it's a workaround because savecopyas doesn't allow you to make any changes.

Hope this makes sense.

But could I do this using save? Off to try.

Apparently not.

I am confused now. Why do you remove the password then save a copy and then reset the password?

I think the problem is that your code is trying to overwrite the copy that is running the code and it can not do that.

I need to save a copy of the file in an alternative location without the password to open. This allows another offsite area to view copies of the files.

I need to reinstate the password so that if an 'inhouse user' tries to open the file they cannot, as they don't know the password. Instead they must go through the Tracker to open the underlying timelines - thus the Tracker maintains control of the inhouse file structure.

It's strange beacus as I said when the user clicks Save the code works perfectly and that is run from within 'thisworkbook' of the timeline form. However if I prompt the code to run from the Tracker (.save, triggers the beforesave) then the code does nothing.

Is there any change if you directly call the SaveAs method in preference to using Save and letting the Event procedure do the work?

Good idea.

Works perfectly, so it must be something it doesn't like about running code triggered on an event within another workbook. I even tries running it again with DisplayAlerts enabled but still no messages of any kind.
It's a bit clunky as it means I'll have to insert the same chunk of code in the Tracker - but I can live with that if it works.

Strange though. I wonder why it's set up that way...

Thanks again for the good idea.