if it was so good, howcome only jcp uses it?  at least they recognize 
that they have a potential
problem with the *only size code.

Pete Austin wrote:
> Yeah, but I remember the first time I printed one of those to a screen.  In
> the mid-80's, working with version 2003.  The BEL character was a ^g, and
> literally (in that day) rang the printer's 'bell'.  Well, when printed, the
> computer beeped.  For about 5 minutes.  My co-workers were laughing.....
>
> -----Original Message-----
> From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Gary
> D. Bligh
> Sent: Monday, January 29, 2007 8:30 PM
> To: 'Leah Halpin'; 'Brian Lehrhoff'; 'Greg Knowles'
> Cc: [email protected]
> Subject: RE: [EDI-L] delimiters issues
>
> Leah, et al,
>
>  
>
> No.
>
>  
>
> I personally like the BEL character as an element separator. The chances are
> extremely slim that a user will enter that on the keyboard.
>
>  
>
> Gary
>
>  
>
>   _____  
>
> From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Leah
> Halpin
> Sent: Monday, January 29, 2007 8:19 PM
> To: Brian Lehrhoff; Greg Knowles
> Cc: [email protected]
> Subject: Re: [EDI-L] delimiters issues
>
>  
>
> but here's the question, are delimiters "data"? VANs will change them with
> regularity, they do not exist in the actual data files, only in the
> translated EDI data, they can even be non-printable and they can be changed
> in any decent translator without regard to the "data" at all, in fact, my
> guess is this whole thing started because the EDI was not set up in
> conjunction with the business who would have said, if asked, "oh, yeah, we
> use * in our files all the time".
>
> Oh, if only someone had an opinion on this.
>
> Leah
>
> ----- Original Message ----
> From: Brian Lehrhoff <[EMAIL PROTECTED] <mailto:blehrhof%40cybernex.net>
> net>
> To: Greg Knowles <[EMAIL PROTECTED] <mailto:gmkhome%40optonline.net> net>
> Cc: [EMAIL PROTECTED] <mailto:EDI-L%40yahoogroups.com> com
> Sent: Monday, January 29, 2007 8:03:27 PM
> Subject: Re: [EDI-L] delimiters issues
>
> never, never, never, never, never, never, never, never, never, never, 
>
> never, never, never, never
>
> change the data. you should know better! does the mailman read your 
>
> magazines before he
>
> delivers them? and, under sox, you probably can't even look at the 
>
> production data. it's a new
>
> world out there. and, if you reject the data, you can't repair and 
>
> remap it ... your partner gets
>
> to resend it. this is where use of a van is good (they can filter the 
>
> data in network) or bad
>
> (ya gotta pay to send the data twice. i hope it's not an 832 or 852.)
>
> consider yourself smacked.
>
> Greg Knowles wrote:
>
>   
>> We were discussing a similar problem the other day.
>>     
>
>   
>> How do folks feel about changing the data? (inbound or outbound)
>>     
>
>   
>> I am concerned about controllership/ SOX/audit/ finger-pointing issues
>>     
>
>   
>> and always try NOT to change the data! (which of course, ignores the
>>     
> inherent change-ness
>
>   
>> of mapping)
>>     
>
>   
>
>   
>> Thanks, 
>>     
>
>   
>> Greg Knowles 
>>     
>
>   
>> EDI Project Leader, GE Supply
>>     
>
>   
>
>   
>> -----Original Message-----
>>     
>
>   
>> From: [EMAIL PROTECTED] com [mailto:[EMAIL PROTECTED] com] On Behalf Of
>>     
> Dale Marthaller
>
>   
>> Sent: Monday, January 29, 2007 3:17 PM
>>     
>
>   
>> Cc: [EMAIL PROTECTED] com
>>     
>
>   
>> Subject: RE: [EDI-L] delimiters issues
>>     
>
>   
>
>   
>
>   
>
>   
>> We also utilize an outbound preprocessor that removes all possible
>>     
>
>   
>> delimiters from the data stream. 
>>     
>
>   
>
>   
>
>   
>> Dale Marthaller (604) 461-6779 
>>     
>
>   
>
>   
>> ____________ _________ _________ __
>>     
>
>   
>
>   
>> From: [EMAIL PROTECTED] <mailto:EDI- L%40yahoogroups. com> com
>>     
> [mailto:EDI- [EMAIL PROTECTED]
>
>   
>> <mailto:EDI- L%40yahoogroups. com> com] On Behalf Of
>>     
>
>   
>> Samantha Scott
>>     
>
>   
>> Sent: Monday, January 29, 2007 9:35 AM
>>     
>
>   
>> To: Art Douglas
>>     
>
>   
>> Cc: Brian Lehrhoff; [EMAIL PROTECTED] <mailto:EDI- L%40yahoogroups. com>
>>     
> com
>
>   
>> Subject: Re: [EDI-L] delimiters issues
>>     
>
>   
>
>   
>> Hey and that's just with my morning coffee in me. I'm actually much
>>     
>
>   
>> nicer
>>     
>
>   
>> after a beer or two
>>     
>
>   
>
>   
>> On 1/29/07, Art Douglas <[EMAIL PROTECTED] <mailto:acd%40ix.netcom> .
>>     
> <mailto:acd% 40ix.netcom. com> com
>
>   
>> <mailto:acd% 40ix.netcom. com>
>>     
>
>   
>
>   
>>> wrote:
>>>       
>
>   
>
>   
>>> It is good go flush out those of our number that have a violent
>>>       
>
>   
>>> temperament.
>>>       
>
>   
>>> Brian and Sam should be lots of fun at our first list-wide party. ;)
>>>       
>
>   
>
>   
>>> PremKumar, you need to decide which of the two uses for asterisk you
>>>       
>
>   
>
>   
>> wish
>>     
>
>   
>
>   
>>> to
>>>       
>
>   
>>> support. Rather than running a pre-processor on outbound data, which
>>>       
>
>   
>>> changes the data and makes the EDI guy responsible for content, change
>>>       
>
>   
>
>   
>> the
>>     
>
>   
>
>   
>>> delimiter. This goes for any level delimiter in the message that might
>>>       
>
>   
>
>   
>> be
>>     
>
>   
>
>   
>>> used in the data. For inbound, just reject the message, contact the TP
>>>       
>
>   
>
>   
>> and
>>     
>
>   
>
>   
>>> negotiate with them to change the contents or the delimiter.
>>>       
>
>   
>
>   
>>> Art Douglas
>>>       
>
>   
>>> Chief Consultant
>>>       
>
>   
>>> Blackwater Network
>>>       
>
>   
>>> 877-464-8915
>>>       
>
>   
>
>   
>>> -----Original Message-----
>>>       
>
>   
>>> From: [EMAIL PROTECTED] <mailto:EDI- L%40yahoogroups. com> com
>>>       
>
>   
>
>   
>> <mailto:EDI- L%40yahoogroups. com>
>>     
>
>   
>> <EDI-L%40yahoogroup s.com> [mailto:
>>     
>
>   
>
>   
>>> [EMAIL PROTECTED] <mailto:EDI- L%40yahoogroups. com> com <mailto:EDI-
>>>       
> L%40yahoogroups. com>
>
>   
>
>   
>> <EDI-L%40yahoogroup s.com>] On Behalf Of
>>     
>
>   
>
>   
>>> Brian Lehrhoff
>>>       
>
>   
>>> Sent: Monday, January 29, 2007 8:05 AM
>>>       
>
>   
>>> To: [EMAIL PROTECTED] <mailto:EDI- L%40yahoogroups. com> com
>>>       
>
>   
>
>   
>> <mailto:EDI- L%40yahoogroups. com>
>>     
>
>   
>> <EDI-L%40yahoogroup s.com>
>>     
>
>   
>
>   
>>> Subject: Re: [EDI-L] delimiters issues
>>>       
>
>   
>
>   
>>> slap the idiot who set it up that way, they should have know better.
>>>       
>
>   
>
>   
>>> Brian Lehrhoff
>>>       
>
>   
>>> EDI Consultant
>>>       
>
>   
>>> 201-913-4506
>>>       
>
>   
>
>   
>>> ----- Original Message ----
>>>       
>
>   
>>> From: "Hodges, Chris" <[EMAIL PROTECTED] <mailto:chodges% 40cswg.com> com
>>>       
>
>   
>
>   
>> <mailto:chodges% 40cswg.com>
>>     
>
>   
>> <chodges%40cswg. com>>
>>     
>
>   
>
>   
>>> To: Samantha Scott <mossmuncher@ <mailto:mossmuncher %40gmail. com>
>>>       
> gmail.com
>
>   
>
>   
>> <mailto:mossmuncher %40gmail. com> <mossmuncher% 40gmail.com> >;
>>     
>
>   
>
>   
>>> premkumar.j
>>>       
>
>   
>>> <[EMAIL PROTECTED] <mailto:premj% 40object- frontier. com> frontier.com
>>>       
>
>   
>
>   
>> <mailto:premj% 40object- frontier. com>
>>     
>
>   
>> <premj%40object- frontier. com>>
>>     
>
>   
>
>   
>>> Cc: [EMAIL PROTECTED] <mailto:EDI- L%40yahoogroups. com> com
>>>       
>
>   
>
>   
>> <mailto:EDI- L%40yahoogroups. com>
>>     
>
>   
>> <EDI-L%40yahoogroup s.com>
>>     
>
>   
>
>   
>>> Sent: Monday, January 29, 2007 9:47:23 AM
>>>       
>
>   
>>> Subject: RE: [EDI-L] delimiters issues
>>>       
>
>   
>
>   
>>> I wouldn't suggest you slap your trading partner but a good hard
>>>       
>
>   
>
>   
>> shaking
>>     
>
>   
>
>   
>>> isn't out of the question.
>>>       
>
>   
>
>   
>>> -----Original Message-----
>>>       
>
>   
>>> From: [EMAIL PROTECTED] <mailto:EDI- L%40yahoogroups. com> com
>>>       
>
>   
>
>   
>> <mailto:EDI- L%40yahoogroups. com>
>>     
>
>   
>> <EDI-L%40yahoogroup s.com> [mailto:
>>     
>
>   
>
>   
>>> [EMAIL PROTECTED] <mailto:EDI- L%40yahoogroups. com> com <mailto:EDI-
>>>       
> L%40yahoogroups. com>
>
>   
>
>   
>> <EDI-L%40yahoogroup s.com>] On Behalf Of
>>     
>
>   
>
>   
>>> Samantha Scott
>>>       
>
>   
>>> Sent: Monday, January 29, 2007 9:41 AM
>>>       
>
>   
>>> To: premkumar.j
>>>       
>
>   
>>> Cc: [EMAIL PROTECTED] <mailto:EDI- L%40yahoogroups. com> com
>>>       
>
>   
>
>   
>> <mailto:EDI- L%40yahoogroups. com>
>>     
>
>   
>> <EDI-L%40yahoogroup s.com>
>>     
>
>   
>
>   
>>> Subject: Re: [EDI-L] delimiters issues
>>>       
>
>   
>
>   
>>> Slap your trading partner and tell them to tell their customer service
>>>       
>
>   
>>> people to QUIT USING THE "*" or any other stupid special notation in
>>>       
>
>   
>>> their text fields.
>>>       
>
>   
>
>   
>>> On 1/29/07, premkumar.j <[EMAIL PROTECTED] <mailto:premj% 40object- 
>>> frontier.
>>>       
> com> frontier.com
>
>   
>
>   
>> <mailto:premj% 40object- frontier. com> <premj%40object- frontier. com>
>>     
>
>   
>
>   
>>> <mailto:premj% <premj%25>40object- frontier. com> > wrote:
>>>       
>
>   
>
>   
>>>> Hi
>>>>         
>
>   
>
>   
>>>> If we have Record delimiter as ( * ) and somewhere in the MSG
>>>>         
>
>   
>
>   
>> segment
>>     
>
>   
>
>   
>>>> we have the same type of delimter appearing in the text. What will
>>>>         
>
>   
>
>   
>> be
>>     
>
>   
>
>   
>>>> the remedy...
>>>>         
>
>   
>
>   
>>>> Example
>>>>         
>
>   
>
>   
>>>> RDEL ( Record delimiter) = ( * )
>>>>         
>
>   
>
>   
>>>> ST~850~0001*
>>>>         
>
>   
>
>   
>>>> MSG~10-20~This is your sample data 128*38*
>>>>         
>
>   
>
>   
>>>> Here 128*38 is the value but it has record delimiter. Under this
>>>>         
>
>   
>>>> circumtance what should be the nessacary step to be taken to
>>>>         
>
>   
>
>   
>> overcome
>>     
>
>   
>
>   
>>>> this issue....
>>>>         
>
>   
>
>   
>>>> Awaiting for your earliest responses... .
>>>>         
>
>   
>
>   
>>>> Thanks
>>>>         
>
>   
>>>> PremKumar.J
>>>>         
>
>   
>
>   
>>>> [Non-text portions of this message have been removed]
>>>>         
>
>   
>
>   
>
>   
>
>   
>
>   
>>> [Non-text portions of this message have been removed]
>>>       
>
>   
>
>   
>>> ...
>>>       
>
>   
>>> 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
>>>       
>
>   
>
>   
>>> ____________ _________ _________ _________ _________ _________ _
>>>       
>
>   
>>> ________
>>>       
>
>   
>>> Need Mail bonding?
>>>       
>
>   
>>> Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users.
>>>       
>
>   
>>> http://answers. <http://answers. yahoo.com/ dir/?link= list&sid=
>>>       
> 396546091>
>
>   
>
>   
>> yahoo.com/dir/ ?link=list& sid=396546091
>>     
>
>   
>> <http://answers. <http://answers. yahoo.com/ dir/?link= list&sid=
>>     
> 396546091>
>
>   
>> yahoo.com/dir/ ?link=list& sid=396546091> 
>>     
>
>   
>
>   
>>> ...
>>>       
>
>   
>>> 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
>>>       
>
>   
>
>   
>
>   
>
>   
>
>   
>
>   
>> [Non-text portions of this message have been removed]
>>     
>
>   
>
>   
>> The Oppenheimer Group ---- CONFIDENTIAL
>>     
>
>   
>
>   
>> This message is for the designated recipient only and may contain
>>     
> privileged, proprietary,
>
>   
>> or otherwise private information. If you have received it in error, please
>>     
> notify the
>
>   
>> sender immediately and delete the original. Any other use of the email by
>>     
> you is
>
>   
>> prohibited.
>>     
>
>   
>
>   
>> [Non-text portions of this message have been removed]
>>     
>
>   
>
>   
>
>   
>
>   
>
>   
>
>   
>
>   
>
>   
>> [Non-text portions of this message have been removed]
>>     
>
>   
>
>   
>
>   
>
>   
>> ...
>>     
>
>   
>> 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
>>     
>
>   
>
>   
>
>   
>
>   
>
>   
>
>   

-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Brian Lehrhoff, EA ([EMAIL PROTECTED])
Messaging Consultant  201-913-4506

Upgrade your Quickbooks for 20% off at http://ea.brianlehrhoff.com
Circular 230 Notice is located at http://ea.brianlehrhoff.com/230notice.html
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%



...
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:
    mailto:[EMAIL PROTECTED] 
    mailto:[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/
 

Reply via email to