|
midrange.com
That worked as long as the character I was starting with was not a blank.
ddh
----- Original Message -----
From: <Jeff@VTINFO.COM>
To: <CODE400-L@midrange.com>
Sent: Wednesday, June 20, 2001 4:08 PM
Subject: Re: Finding Strings starting with blanks in Code
>
> If you press the Options button on the Find window, you can search within
> specific columns. In your case I guess you would want to search only in
> columns 19-20.
>
> Jeff Morrill
>
>
>
>
> "Dwight HoganCamp"
> <Dhogancamp@Ruger. To:
<CODE400-L@midrange.com>
> com> cc:
> Sent by: Subject: Re: Finding
Strings starting with blanks in Code
> owner-code400-l@mi
> drange.com
>
>
> 06/20/01 03:38 PM
> Please respond to
> CODE400-L
>
>
>
>
>
>
> I tried both the double and single quote. What I am finding right now is
> that if I want to find a character string other than blanks, I can enter
> the
> string and it finds it.
>
> Right now I am trying to insert prefixes in front of fields names in DDS.
I
> need to specify the blank because I want to insert it at Position 19. The
> character string in 19 & 20 where I am inserting may be repeated in the
> field and some attempts I have made have inserted the prefix two or three
> times in the name which is undesirable.
>
> I know there are no blanks in the name so if I scan for <space>PC it will
> get the beginning of the field name.
>
> I have tried both single and double quotes around it like we used to do in
> SEU, and I have tried <space> PC like someone suggested, and I tried just
> typing in a space. I had the same result each time "string - not found".
>
> Thanks for any input you may have
>
> Dwight @ Ruger
>
> ----- Original Message -----
> From: <batthish@ca.ibm.com>
> To: <CODE400-L@midrange.com>
> Sent: Wednesday, June 20, 2001 2:52 PM
> Subject: Re: Finding Strings starting with blanks in Code
>
>
> > Hi Dwight,
> >
> > Are you searching in CODE using the single quote (') or double quote(")?
> > If so then that would be the reason why it is not finding the string.
> > You shoudl just be able to type the PC with the space, without any
> quotes.
> >
> > Hope this helps!
> >
> > Violaine Batthish
> > CODE/400 Project Lead
> > batthish@ca.ibm.com IBMCA(BATTHISH)
> >
> > CODE/400 page: http://www.ibm.com/software/ad/varpg
> > WDT/400 Support :
> > http://www.ibm.com/software/ad/wdt400/update_downloads.html
> >
> >
> >
> >
> > "Dwight HoganCamp"
> > <Dhogancamp@Ruger. To:
> <CODE400-L@midrange.com>
> > com> cc:
> > Sent by: Subject: Finding
Strings
> starting with blanks in Code
> > owner-code400-l@mi
> > drange.com
> >
> >
> > 06/20/2001 02:01
> > PM
> > Please respond to
> > CODE400-L
> >
> >
> >
> >
> >
> > Ok
> >
> > When I worked with SEU I could type either ' PC' or " PC" in the command
> > line of SEU, or on the Find/Change Options screen by pressing F14.
> >
> > When I do the same thing with Code it says there is nothing, even though
> I
> > can see what I am looking for.
> >
> > I am trying to insert XRE in front of 106 fields that starting with PC
in
> a
> > data dictionary of 1400 lines.
> >
> > I got this one to work by excluding the first 156 lines then the last
> 1138
> > lines then finding PC in 19 and 20 and replacing it with XRE.
> >
> > Is there some way to change the lines that are excluded. The SEU version
> of
> > this worked hours ago, but it didn't like me inserting more characters
> than
> > I am scanning for even with allow data to shift. So I had errors on two
> > lines that way.
> >
> > Once I finally got code to work, it changed just the ones I wanted the
> way
> > I
> > wanted them. Nice job on that one, but it is still too cumbersome.
> >
> > +---
> > | This is the CODE/400 Mailing List!
> > | To submit a new message, send your mail to CODE400-L@midrange.com.
> > | To subscribe to this list send email to CODE400-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to
> CODE400-L-UNSUB@midrange.com.
> > | Questions should be directed to the list owner/operator:
> larry@paque.net
> > +---
> >
> >
> >
> > +---
> > | This is the CODE/400 Mailing List!
> > | To submit a new message, send your mail to CODE400-L@midrange.com.
> > | To subscribe to this list send email to CODE400-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to
> CODE400-L-UNSUB@midrange.com.
> > | Questions should be directed to the list owner/operator:
> larry@paque.net
> > +---
>
> +---
> | This is the CODE/400 Mailing List!
> | To submit a new message, send your mail to CODE400-L@midrange.com.
> | To subscribe to this list send email to CODE400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
CODE400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: larry@paque.net
> +---
>
>
>
>
> +---
> | This is the CODE/400 Mailing List!
> | To submit a new message, send your mail to CODE400-L@midrange.com.
> | To subscribe to this list send email to CODE400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
CODE400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: larry@paque.net
> +---
+---
| This is the CODE/400 Mailing List!
| To submit a new message, send your mail to CODE400-L@midrange.com.
| To subscribe to this list send email to CODE400-L-SUB@midrange.com.
| To unsubscribe from this list send email to CODE400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: larry@paque.net
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
