Hi MoonWolf,

I regard it as a potential threat if detailed document and transaction data are being transmitted. In a corporate environment I would certainly disable it at the desktop level, as it will only confuse users and generate useless helpdesk traffic. Anyway, most crashes are caused by applications software conflicts or errors, and have nothing to do with the operating system.

I have worked for many years in applications development using structured methodologies. The rules are quite simple: if data content (either transaction or document) cause a system to crash, this should be detected at the unit testing or systems testing phases of the development cycle.

If the system fails to process data correctly (NOT a crash), this should be detected at the user acceptance testing phase, or at the very latest during the "pilot" run.

Now, with commercial, off the shelf software, you have some difficulty with the user acceptance testing phase, as you are not the user. This is where alpha and beta testing come in. But, just like an in house development, crashes due to data content should not reach either of these phases.

This is why I am arguing that detailed transaction data should not be included. They are irrelevant at this stage in the proceedings, and may represent a security compromise.

I am assuming that Microsoft know, understand and apply structured methodologies, and have managed to progress beyond CMM level 1