michaelnol was thinking very hard :
On Feb 8, 8:01*pm, GS wrote:
Jim Cone explained on 2/7/2012 :

As I said "Never used them".
A quick look at help says the Siicers parent is the workbook not the
worksheet.
There is also a SlicerCache in there somewhere.
Looks like a convention hierarchy of a slicers collection with slicer
objects.
'---
Jim Cone
(he discovered he was only looking at the tail of the elephant)

Thanks again, Jim!
Ok, so we may be barking up the wrong tree with putting focus on
protection parameters and UserInterfaceOnly. One would think, though,
that Excel native code would respect that setting, IMO!

--
Garry

Free usenet access athttp://www.eternal-september.org
ClassicVB Users Regroup! comp.lang.basic.visual.misc

I guess it needs to be some code that onclick of a slicer the
protection is removed to allow the data to refresh and then the
protection is reapplied. It is the onclick of a slicer that has me
stumped....

My thinkng is that the protection parameters should be respected by
built-in processes and so, if correctly applied, the data should
refresh. Did you try 'resetting' the protection as per my suggestion?

--
Garry

Free usenet access at http://www.eternal-september.org
ClassicVB Users Regroup! comp.lang.basic.visual.misc