Thanks, that was the solution! I find it interesting that there is NO mention of this problem on the Microsoft Knowledge Base, although I found it, too, by searching from Google. It is not actually a bug in their product, but since it exists, it would have been nice for them to list it. And wise as well, because I very nearly pitched .net right out the window over this.
|