Ian,

Thanks for the response.

I searched the MS knowledge base and found the same exact thing just after I noticed the problem the first time. It unfortunelly referenced a situation that occurred in 2003 and is not applicable in my case.

Thanks again. Login to read more.