It’s been rumored for a while already, but the UK’s Post Office has now confirmed that it’s to launch a new mobile phone network later this year. The state-owned Post Office already offers its own home-phone and broadband service, so a move to become a mobile virtual network operator (MVNO), piggybacking off EE, may not be entirely surprising. It’s also in line with other high street brands, such as Sainsbury’s, Asda and Tesco, which offer their own mobile phone services. The Post Office’s new service will launch in the autumn, and will be available online and through 50 branches, before…
This story continues at The Next Web
In Part One, we considered the problem of determining what actually triggered a PivotTableUpdate (or it’s equally gormless twin, the PivotTableChangeSync event), with a view to identifying when a specific PivotField is filtered. Today we’re going to take a look at how we can find out more about what triggered those events. And what better place to glean information about the last action the user performed than here:
That’s right, the Undies stack. (That’s what we call it down-under). Or rather, the Undo stack to you uptight northerners. (Ok, enough of the innuendo and Double entendre.)
Go on, then…show us what’s in your undies…er…undo stack, Jeff:
Wow: all of the above relate to some kind of action on a PivotTable. If only we could access that list, we’d have a pretty rich source from which to answer the title of this post. And we can indeed do just that.
If you want everything in that list, then you can use this code from MVP Siddharth Rout at msdn:
UnDoList(i) = xlApp.CommandBars("Standard").Controls("&Undo").Control.List(i)
Next
…and if you just want the last undo item, you can use this:
Let’s take a look at how all the different things that raise a PivotTableUpdate event get reflected in that Undo list. If an action isn’t listed in the below table, then as far as I know from my rather in-exhaustive testing, it doesn’t raise a PivotTableUpdate event.
There’s a few things worth noting about the above.
- Firstly, we can now clearly determine whether the update was caused by filtering, a refresh, a structure change (in which case the Undo Stack just says ‘Pivot’, or other less common tweaks.
- Secondly, while we can use this to confirm whether or not a PivotTableUpdate event was in fact caused by someone adjusting a PivotFilter, we still can’t tell which filter.
- Thirdly, it’s surprising just how many things trigger an update – which is why it will be good to call out filter changes explicitly in the event that we want to sync lots of large pivots.
- And finally, one of the actions – adding/amending/deleting a Calculated Field – actually clears the Undo Stack. How weird is that?
Okay, that’s enough for today…I’ve got to go cook my dinner. (My wife is in Spain with the kids, and so apparently it won’t cook itself). Tune in next time, when we’ll look at how we can write a routine that leverages off the undo stack, and that also helps us determine not only that a PivotField was filtered, but which PivotField it was.
This is how much crazy Jack Ma needed to turn Alibaba into a multi-billion dollar giant
“Crocodile in the Yangtze” starts off with a shot of Alibaba founder Jack Ma dressed up in an outlandishly outrageous rock star outfit and performing on stage in front of thousands of people. It wouldn’t be surprising if the first word that popped into your mind was “crazy.” And Ma was indeed crazy to a certain extent — well, that goes without saying considering that even as an English teacher, he went ahead to chase the dream of starting an e-commerce firm from scratch, taking on global multi-billion-dollar companies including eBay. “eBay is a shark in the ocean. We are a…
This story continues at The Next Web