Thanks.  We're looking into this one.  It appears to be a caching issue.  We'll track it down.