Thanks for the info. If I ever strike it I will know where to look. It looks like Microsoft did finally fix it.
Responses to this message: