Slicer macro leaves project loaded in VBA Editor when workbook is closed

I am using some code that I have adapted from
http://stackoverflow.com/questions/2...ll-pivot-table

The code is designed to make it easy for users to disconnect / reconnect slicers to pivot tables. The code works, but has an unfortunate effect on the way in which Excel manages VBA projects.

With my setup of 32 bit Excel 2010 running in Windows 7, if the macro is run and the workbook is then closed without saving, an orphaned copy of the VBA project remains visible in the VBA Editor and this can only be cleared by closing and restarting Excel.

Here is the code, and I've attached a workbook containing some data, slicers and buttons to run the code.

Has anyone else come across this quirk? Is there another approach that I could take to automate disconnecting and reconnecting slicers to pivot tables which does not mess up the way in which the VBA editor manages its memory?

Please Login or Register  to view this content.

I seem to have fixed this bug by not using the slicer object. My revised code for the ManageSlicer function is

Please Login or Register  to view this content.

Late to the party... Just wanted to point out that it's the use of oSlicer.SlicerCache, in the original post, that makes the workbook stick around in the VBA editor. The workaround is to get to the SlicerCache through another path, as in Peter's second post.