In message <[email protected]>, eppyebots <[email protected]> writes >I think I got rid of the 'horrible' errors. Try again ;-) I really >appreciate your feedback.
I tested again (with the same buggy interchange) and the report was much more understandable and was, to my mind, acceptable. The only query I would have concerns information like: line 13 pos 1: The interchange I sent was split with one segment per line, so that is understandable. If it had been sent as a stream would the above report have been line 1 pos nnn:, where nnn was the offset into the interchange of the offending segment, or do you have some blocking convention? Regards Chris -- Chris Johnson mobile:+44 (0)7785 302122 Fax: +44 (0)870 0519 818 EDI website http://www.edimatrix.co.uk EDIMatrix Ltd work: 0844 414 6386 or +44 20 8778 1402 Registered in UK no. 2777624 Reg.Office: 34 Sydenham Rd, London SE26 5QF ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
