One thing we simply MUST do before shipping this code is to get rid of all these toasts that pop up as the program is going through its paces. I promised a few weeks ago I'd look into that. It's an easy fix and I've written up a summary in the form of a blog entry. <http://blog.nelsondev.net/?p=510> http://blog.nelsondev.net/?p=510 I propose on a first pass basis to make the global makeToast() and just comment out its action for a compile-time solution when we're ready to "ship". Fancier versions can follow. If I write an initial version of makeToast() I'll include a parameter so the caller can specify whether it's a toast we want users to see, and one that's only for diagnostics. Peter PS - I will NOT be at next Tuesday's meeting - have to go with my wife to Dana Farber.