Forum Discussion
Can no longer refresh data in a Protected Workbook since Excel version 1803
- Jun 04, 2018
Hi there,
The fix was deployed for the following Office versions:
- Version 1803 (Build 9126.2196) and later
- Version 1804 (Build 9226.2135) and later
- Version 1805 (Build 9330.2017) and later
Hope this helps.
Guy.
- Excel Team
I have this same issue, the only work around I've come up with so far is to use a macro to run when the workbook is opened, unprotect the workbook, refresh the data (not in the background) and then lock the workbook. It's a pain in the arse since I have to change many different tools. Please roll this change back!
Hey David,
Can you share your macro? I don't think it'd work for my situation but it might help others in the same pickle.
- David BranderApr 11, 2018Brass Contributor
Hi Brian,
Sure, happy to. I'm no Excel expert but put this together this afternoon. Use at your own risk.Add this to the workbook macro section:
Private Sub Workbook_Open() Call RefreshQuery End Sub
Add this to a module:
Sub RefreshQuery() ThisWorkbook.Unprotect strAdminPassword Application.EnableEvents = False 'This value check looks at a formula I have in the workbook. if you haven't refreshed within a week you get a 1 If Range("SECTOR!B33") = 1 Then StartTime = Time ' Show 'Updating..'-message Not sure if the timer is needed any more, it was legacy from something else but it works with it, so hey if it ain't broke... ActiveSheet.Shapes.Range(Array("Rectangle: Rounded Corners 1")).Visible = True nSec = 0.1 + Timer While nSec > Timer DoEvents Wend 'Change "Connection" to the connection name you have. ActiveWorkbook.Connections("Connection").Refresh ' Remove 'Updating..'-message ActiveSheet.Shapes.Range(Array("Rounded Rectangle 1")).Visible = False nSec = 0.1 + Timer While nSec > Timer DoEvents Wend End If 'This section below is more specific to my use case - so I track when this was last refreshed, if it's older than a week I'll force the user to refresh to continue to use the workbook. Dim cell As Range Dim rng As Range Dim RangeName As String Dim CellName As String 'Single Cell Reference (Workbook Scope) RangeName = "REFRESH_DATE" CellName = "O1" Set cell = Worksheets("UCON Pricing Tool (2016)").Range(CellName) ThisWorkbook.Names.Add Name:=RangeName, RefersTo:=cell Range("REFRESH_DATE").Value = Date Range("REFRESH_DATE").NumberFormat = "dd/mm/yyyy" Application.EnableEvents = True ThisWorkbook.Unprotect strAdminPassword End Sub
You may need to edit the code to get what you want from it, but it's a base. I am still testing this with my workbooks so it may not be final. Effectively, use at your own risk/understanding. It may work for you, it may not. Currently, it seems to work for me but it's a pain in the arse of a workaround.
You'll need to disable background refresh for your connection, and disable refresh on opening.
David- Petr PotociarApr 16, 2018Copper Contributor
Thank you David very much for the macro, it works again!
I encountered the same problem, my excel needs to download exchange rates and needs to be protected. Since update I can no longer have the workbook protected and refresh connections.
When using macro to refresh connections, it is necessary to disable refresh of connection on the background and to disable refresh of connection when opening the workbook, otherwise macro locks the workbook before connection is updated / shows message, that the workbook is protected and cannot be changed.
Anyway I would appreciate solution from Microsoft and if possible - without necessity to use macros at all. The last update is a real pain in the arse.
- Andrew NevardApr 19, 2018Copper Contributor
Here is some code that I adapted for other purposes a while back. I have added ThisWorkbook.Unprotect and ThisWorkbook.Protect to it to get around the bug. These are in events that are triggered before and after a refresh so you can have a background refresh and the workbook will only be protected again once the AfterRefresh event is triggered. Use it at your own risk, but it is serving me well.
In ThisWorkbook add the following declaration
Dim QueryAnswer As clsQueryDone
Then add the following to the Workbook_Open event. Make sure to change the sheet name and query number to the correct ones.
Private Sub Workbook_Open() 'Associate QueryAnswer with QueryTable 'Create query class object Set QueryAnswer = New clsQueryDone QueryAnswer.HookUpQueryTable Sheets("Sheet1").QueryTables(1)
Set up a Class Module called clsQueryDone and add the following to it:
Private WithEvents MyQueryTable As QueryTable
Private Sub MyQueryTable_AfterRefresh(ByVal Success As Boolean)
ThisWorkbook.Protect strMasterPwd
If Success Then
'Do whatever you want
Else
MsgBox "There has been an error with the Query Refresh", _
vbOKOnly Or vbCritical, "Refresh Error"
End If
End SubPrivate Sub MyQueryTable_BeforeRefresh(Cancel As Boolean)
ThisWorkbook.Unprotect strMasterPwd
'and do whatever you want
End SubFriend Sub HookUpQueryTable(qt As QueryTable)
Set MyQueryTable = qt
End SubAndrew
- Andrew NevardApr 13, 2018Copper Contributor
Hi David,
Correct me if I am wrong, but shouldn't the last line in your RefreshQuery sub actually be:
ThisWorkbook.Protect strAdminPassword
- David BranderApr 13, 2018Brass ContributorYes, it should! I realised my mistake when I deployed it to a couple of our tools today.
It isn't as elegant solution as I'd like, preferably I wouldn't want to have to implement a solution, but it does the job for the moment.
David
- Marcel PayensApr 11, 2018Copper Contributor
Be aware, with a macro solution, that you may have to remove all checkboxes for 'refresh automatically when cell value changes ' for all queries in your workbook, and to refresh these queries with a command well from your macro. Similarly you will need to disable 'Refresh data when opening the file' and possibly also for background refresh. It is really a pain.
- Marcel PayensApr 13, 2018Copper Contributor
All,
I think if we want Microsoft to move and take some action to correct this, we need a lot more complaints in this thread than those of the few poor souls that are here now, who actually understand what is wrong. Suggest to mobilize your customers / colleagues to join in here.
- Alex LushApr 13, 2018Iron ContributorI logged a call with Office 365 a few days ago to determine if this was a bug or an intended functionality change. Watch this space. I cited this thread in the ticket hopefully they are seeing people's frustration!! I will update this thread as I hear more.