Ted - thanks for that lengthy explanation - and for making me "see the light"
as to why I can' see that character in VFP. And, Thanks ALSO for that humorous
last line - as its always nice to get a chuckle here at work!
Fred - I was also looking over your response - and in particular when you wrote:
string to number:
VAL("0x5F") or EVALUATE("0x5F") -> 95
Then it dawned on me - and somebody should have smacked me in the head on that
one. Since, they gave me a Hex number, I should simply have converted it into a
Decimal number - and any programmer with even a Half a Brain should know how to
convert it - and then use that decimal number with the CHR() function to give
me what I needed. Of course, your command to convert the Hex # into a Dec. #
also does the job. Although, it should be more fun to actually convert the
number on my own. Actually - about 1.5 years ago, when my son was 9 - one
evening I started telling him about Binary and Hexadecimal number systems, and
showing him how to convert numbers between Hex & Dec, or Bin & Dec - and then
even showed him how to do Hex or Bin Math Addition. He loved it - and for days
after - would beg me to give him math problems based upon Hex or Bin!
OK - back to work for me...
Thank you ALL for your input - as usual - the ProFox list ROCKS!!!
-K-
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Ted Roche
Sent: Thursday, August 16, 2012 2:49 PM
To: [email protected]
Subject: Re: EDI, Hex & VFP - Oh My...
Most of the internet is speaking Unicode UTF-8 or -16 these days.
ASCII is really only defined for the first 128 characters (7-bit) and
the 'extended ASCII character set' from 128 to 255 is different from
different vendors; IBM implemented the upper characters of foreign
entities and line-and-box characters one way, Microsoft another, and
so forth. Microsoft uses an ANSI character set. DOS implemented code
pages as a kludge. Try some of those characters in FoxFont and in
Arial and you'll see the difference.
So, that's the long way of saying that the reason you can't cut and
paste from email (ANSI or Unicode) into VFP is that the two are
speaking incompatible dialects.
So, your vendor, in choosing an upper 8-bit character, is implementing
a "non-standard EDI format" which I can't even type without lol.
On Thu, Aug 16, 2012 at 2:34 PM, Kurt Wendt <[email protected]> wrote:
> 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: [email protected] [mailto:[email protected]] On
> Behalf Of [email protected]
> Sent: Thursday, August 16, 2012 1:44 PM
> To: [email protected]
> 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" <[email protected]>
> To: <[email protected]>
> 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-
_______________________________________________
Post Messages to: [email protected]
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.
