KL::It would not help Microsoft ship a better product.

Understood; well taken.



KL::The only way to have a bug fixed is to have it within the "internal" Microsoft bug tracking database, not on a web site list.

The intent is not necessarily to hasten repair (although that would be a nice side benefit were it to occur -- that's what I was getting at earlier), but rather to provide us a common means of getting a grasp on issues we need to watch out for when developing for our own clients.

As I mentioned to Mike Beane, the current method of wading through the KB to MAYBE find something clearly isn't working. There's no way to know whether a submitted report actually became a real bug. Also, when searching the KB, one has to know what one is looking for in order to find it (if you get my meaning).

Then, even when something is found, the KB has no means of linking resolutions (assuming they're posted at all) to the original issues. It's frustrating for us out here.

We need a central registry for the community; fields for KB URLs would help.