Honestly - I'm not sure why the character is Visible in the e-mail below, but, when I try to cut&paste it into VFP - its NOT Visible at all.
Not sure about ANSI 837, but, I will assume its standard EDI - but, different from the type of stuff I deal with. Mine is for sales orders(850), Advance Ship Notice/ASN(856) and Invoices (810). Actually - I find it VERY ODD that they are using this particular character - because, in other EDI files, its usually characters like you described below... -K- -----Original Message----- From: profoxtech-boun...@leafe.com [mailto:profoxtech-boun...@leafe.com] On Behalf Of kamcgin...@gmail.com Sent: Thursday, August 16, 2012 1:44 PM To: profoxt...@leafe.com Subject: Re: EDI, Hex & VFP - Oh My... If this is for a ANSI 837 transaction set, for example: sending claims to Medicare: Element separator: 124 '|' Sub-element separator: 094 '^' Segment terminator 126 '~' Those are all ASCII, visible, printable codes so you should not have to use the hex value. ----- Original Message ----- From: "Kurt Wendt" <kurtwe...@waitex.com> To: <profox@leafe.com> Sent: Thursday, August 16, 2012 9:54 AM Subject: EDI, Hex & VFP - Oh My... Hey folks, I'm a little stumped on something. Here at my day job, I have to deal with EDI stuff - and I do it all the time. But, a new upgrade for this one Trading Partner is requiring a strange code to be sent back - as displayed in the line below. Strangely enough, I was surprised to see the character appear below (after the "to" and before the "or") - since, when I tried to insert this Text into VFP - just to print on-screen, the character shown below does not appear - but, instead a blank space appears in VFP. So - of course, I am having difficulty figuring how to send back this character. Here is the line of instructions on this particular EDI upgrade: o ISA11 needs to be changed to ¬ or Hex 5F As such, I figured I would try to implement via the Hexcode. But, how exactly do I use HexCodes in VFP. I know the ASC() and CHR() commands, but, AFAIK - that's for purely Ascii code and NOT for Hex code. Any advice would be greatly appreciated! Thanks, -K- Senior Developer Waitex Information System, Inc. P Save a tree. Don't print this e-mail unless it's really necessary. --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/289ea162f5642645b5cf64d624c66a140e260...@us-ny-mail-002.waitex.net ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
