One more followup – this was not detected as an issue in BT2006 or BT2004 because the Covast schemas defined the AN properly, as a string.
I can see how the acronym “AN” might have been misleading to Microsoft, but I can’t imagine how this error went to gold bits. Is anyone really using R2 in production? Because it seems like a flaw this big would have revealed itself by now and been corrected if anyone were really using R2 for production EDI.
Also, why are there no 4060 EDI schemas? They stop at 4050. Is microsoft going to step up to bat wi th the schemas? Seems like they need a service pack release for R2 before this thing is ready for prime time.
– weak architect