Thursday 13 December 2007

Why did I just get multiple invites and cancellations for the same meeting? Is this thing on?

A while back I posted about common ways meetings can go missing, one of which is when a distribution list is invited to a meeting.
Today I saw an interesting 'feature' of how inviting a distribution list (DL) then trying to make changes later can really confuse things.  Our team got two invites and a cancellation to the same meeting, and the organiser couldn't work out how it had happened. covers the basics of what the organiser and invitees see, but it doesn't really explain how that occurs. So for the record, here's a worked example (you know how I love those):
  • I've been asked to create the invite for my team's offsite team-building exercise (read: we're going to the pub)
  • My team are all members of a DL called BigTeam, so I send the invite to them (ignoring the great advice I usually encourage everyone else to follow that says never invite a DL without expanding it, especially one you're a member of)
  • I realise later that the BigTeam DL also includes some guys who work at a remote location to us - remote enough that they probably don't want to know the details of some drink-up they won't be able to get to. So I go back into the meeting and remove them.
  • Here's the critical bit: because they were invited as part of the BigTeam DL, to un-invite them I have to expand out the DL, then remove them from the expanded list.
  • Here's the bit they don't explain in the KB article: Outlook just sees addresses in the invitee list. It doesn't much care if they're DLs or individuals. It sees that the BigTeam DL has gone from the invitee list, and a whole load of individuals have suddenly appeared. (It just sees the difference between how the invitee list looked before and how it looks now, so isn't 'aware' that a DL was expanded to get to where we are now.)
  • Outlook does what it always does in these situations: it sends a cancellation to all the addresses that were in the invitee list but aren't any more (i.e. the BigTeam DL) and sends an invitation to all the addresses that are in the invitee list that weren't before (i.e. the people whose names are left after I removed our far-flung colleagues).
  • Everyone gets a cancellation (because a cancellation was sent to the BigTeam DL), and those lucky enough to still be invited get a new meeting request. It doesn't appear to make sense, but this is Outlook behaving as it was designed.
The up-side if you're using Outlook 2007 is that at least it doesn't allow you to process meeting invites/updates/cancellations in the wrong order, which would probably confuse things even further. But the basic behaviour is still the same.
I hope this helps explain things if this has been causing you the same kind of confusion it caused in our office today!

Wednesday 12 December 2007

Cool Excel tip to make sure VLOOKUP continues to work if columns move

I'm a fairly advanced user of Excel so generally I find hints and tips fall into two categories: either I already know them, or they relate to features I never use (like functions way beyond my meagre grasp of maths or finance). But today I read a really cool tip that 1) I'd definitely use and 2) it never occurred to me to try before.

This is from David Gainer's blog, I hope he doesn't mind me reproducing it here...

Here’s a trick to using VLOOKUP with tables. VLOOKUP isn’t table-aware, so the third argument, col_index_num, is still a number and not, say, a column name when used with Tables. Next time you use VLOOKUP on a table, use the following formula for the third argument instead of an index number:

MATCH( TableName[[#Headers], [ColumnName]], TableName[#Headers], 0)

Substitute ‘TableName’ with the name of the table you are looking up, and ‘ColumnName’ for the name of the table column you want to index into. This, in effect, gives you a tight pointer to the column that does not break if the column name changes or if the column is re-arranged in the table, thereby providing a more robust alternative to using a numerical index.

Office 2007 SP1 is available

See for details.

Invariably there are a few new hiccups discovered in the early days of a major Service Pack, so if your PC is critical to what you do then it's usually a good idea to hold back a few days. Let other more intrepid (or more foolhardy, depends on your view) folks try it out and see how much shouting there is on the blogs and newsgroups before you install it for yourself.

Of course, if SP1 contains a fix for a problem that's been bothering you then you may want to go ahead now anyway.

Meanwhile, I'll be one of the intrepid/foolhardy people installing mine tonight. (But then I've already been running the Beta on a test machine for a while.)

Creative Commons License This work by TechieBird is licensed under a Creative Commons Attribution-No Derivative Works 2.0 UK: England & Wales License.