Memo Fields and Export Issues

Stanley - stanlyn.com stanley at stanlyn.com
Mon Mar 23 20:32:38 PDT 2015


Thanks Ken,

Thanks for the pointer.  I noticed almost no documentation, so what would a command look like that converts cr, lf, space, crlf to?

xx=212		(212 is the memo field)
bb = XLATE(xx, from_expr, "-CR-", "-LF-", " ", "-CRLF-") 

What would the from_expr look like in the above command?                

Thanks,
Stanley




-----Original Message-----
From: Ken Cole [mailto:ken.m.cole at gmail.com] 
Sent: Monday, March 23, 2015 11:12 PM
To: Stanley - stanlyn.com
Subject: Re: Memo Fields and Export Issues

Stanley,

xlate is a filePro command from around version 4.5.

your issues are not memo related specifically but string related.

Ken

On Tue, Mar 24, 2015 at 2:05 PM, Stanley - stanlyn.com <stanley at stanlyn.com> wrote:
> Hi Ken,
>
> And what is xlate?  Part of filepro?  3rd party?
>
> How would it be implemented as part of an export routine?
>
> Are these issues related only to memo fields?
>
> Thanks,
> Stanley
>
>
>
>
> -----Original Message-----
> From: Ken Cole [mailto:ken.m.cole at gmail.com]
> Sent: Monday, March 23, 2015 9:42 PM
> To: Stanley - stanlyn.com
> Subject: Re: Memo Fields and Export Issues
>
> Stanley,
>
> That will trim leading and trailing spaces but not any other, even "non-printable", characters as they may be non-printable but they are not a space.
>
> You will need xlate or similar to remove any other extraneous characters not required.
>
> Ken
>
> On Tue, Mar 24, 2015 at 12:07 PM, Stanley - stanlyn.com <stanley at stanlyn.com> wrote:
>> Hi,
>>
>> I'm trying to export data from a filepro memo field in 254 character chunks.
>>
>> 1st problem was embedded carriage returns and line feeds inside the 
>> memo field causing the export command to close the field assignments prematurely.
>> I removed them and now it properly processes all the chunks except 
>> the last one.  I suspect a carriage return as the last character is 
>> causing the problem.  I suspect that because the memo field on the 
>> entry screen shows an ending/closing CR character as the last character.
>>
>> I'm attempting to trim the memo value by using:         (212 is memo table
>> field)
>> mm(16,memo)=212 ; aa=""{mm{""
>>
>> 1. Will that perform a trim on both sides of mm, effectively 
>> all-trimming it?
>> 2. Would it remove or include the trailing spaces and/or cr/lf 
>> non-printable characters?
>>
>> 3. In code what is best way to replace all cr, lf, and/or crlf that 
>> the memo contains with a printable string such as "CRLF", so later in 
>> a post process I can search on CRLF and substitute back to retain 
>> original format?  Some code would be very helpful.
>>
>> 4. Is there any other issues with exporting memo fields that I need 
>> to know about?
>>
>> Using SCO 5 and filepro processing 5.0.14R4
>>
>> Thanks,
>> Stanley Barnett
>>
>>
>>
>>
>>
>> _______________________________________________
>> Filepro-list mailing list
>> Filepro-list at lists.celestial.com
>> Subscribe/Unsubscribe/Subscription Changes 
>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes 
> http://mailman.celestial.com/mailman/listinfo/filepro-list



More information about the Filepro-list mailing list