[Brian]

Wow, sorry about the trouble here - looking at the development database, it looks like one of our testers actually identified this issue back in 2008! (This forum thread is also only the second time it's been reported by a customer, which is also pretty surprising.)

In any case, I added a link to this thread to the database. (In case other folks encounter this, please let us know - duplicate reports help us direct developer time at the issues that folks need fixed.)