Run-time error '1004': Method 'SaveAs' of object '_Workbook' failed on SharePoint

I've never used sharepoint but this seems to come up a few times if you search for your post title
This poster put it down to the file already existing in SP.

https://www.reddit.com/r/excel/comme..._just_started/

If so it would be interesting to know if you try saving without a prompt (ovewrite existing) if it stops.

Please Login or Register  to view this content.

It's difficult to be sure as SharePoint seems to behave inconsistently at times, but I've given this a try and if I set DisplayAlerts = False as per your code above, I obviously don't get the warning that the file already exists but I do still get the same error 1004 message and my code stops at NewWB.SaveAs. However, it looks like it does save the file, although when I open the resulting file it tells me "UPLOAD BLOCKED" and tells me to save a copy, so there definitely seems to be some sort of conflict with SharePoint.

If I use:

Please Login or Register  to view this content.

I do get the "file exists" warning and it appears to save ok, but I have now noticed the same issue with "UPLOAD BLOCKED" when opening the resulting file and, in file explorer, the file seems to be stuck on sync pending indefinitely.

In both cases, the file saves fine if the filename doesn't already exist.

SharePoint seems to be the culprit, but it would be good to know if there's a fix for this.

Can you delete the old sharepoint file if it exists prior to saving the new one, as you intend to overwrite it anyway?

Yes, I guess that would work as a workaround, but it's just frustrating that this doesn't work as you'd expect. The SaveAs function is obviously designed to look for an existing file, and it does so perfectly on a local drive, so must be something to do with SharePoint lag.

As a reminder VBA was created near the end of last century based on his gran'pa' the BASIC created in the 80's on PC but started in the 60's
so obviously SharePoint did not ever exist at that time !
Just warming a couple of neurons you can first save it on a local drive
then use a Windows feature (like FSO) to copy / move the file where necessary …