If you look forever in the microsoft technical area you will find the same method to correct this issue. So hats off to Rick for finding it for us. Once Rick posted the fix I could find it in Microsoft.com
Blue Man Group There is no such thing as stupid questions. Just stupid answers
