Importing/exporting data with carriage returns (I Think)

[Fairlight]

Why not just translate the \r to \001 before import, and then whenever
outputting or otherwise referencing the data on the way out, translate \001
to \r?

m->

On Fri, Aug 25, 2017 at 02:54:31PM -0500, Richard D. Williams via Filepro-list thus spoke:
> Top Post
> 
> Mike,
> 
> You have a real problem here.  Typically we need some unique
> character to indicate the end of a row.
> That usually is a carriage return.  If you have carriage returns
> inside any column in the spreadsheet and you use
> filepro's import, that would be understood to be the end of the row.
> 
> I do not know any way you can read this into a file the normal way.
> 
> But, if you are willing to do some manual manipulation, there is a solution.
> 
> Working on the assumption there is a column with some unique
> identifier for that row why not;
> 
> 1) make a copy of the original.
> 2) working on the copy, remove the column that contain the carriage return.
> 3) save as a csv file
> 4) import the remain columns into your file using the file import commands
> 5) make another copy of the spreadsheet
> 6) remove all columns except the column containing the key
> identifier for that row and the one containing the carriage returns.
> 7) add a column to the end and place a ~ in that column for each row
> 8) save as a csv file
> 9) now import this spreadsheet using the file import command and set r=~
> 10) use the key identifier column to place the text into the memo
> field for each record.
> 
> Hope this helps,
> 
> Richard D. Williams
> 
> On 8/25/2017 2:10 PM, Mike Fedkiw via Filepro-list wrote:
> >Okay, so if I remove the carriage returns before importing the
> >data using xlate I'm assuming it would all just wind up as a
> >continuous line of data. If that's right, is there any way of
> >importing the data retaining the spacing between the data so it'll
> >be there when exported. Although I've already had issues with the
> >data not exporting after the first carriage return last time I
> >tried it.
> >
> >Mike
> >
> >
> >On 8/25/2017 1:58 PM, Chris Rendall via Filepro-list wrote:
> >
> >>You can use the XLATE command to remove the carriage return in a
> >>CSV import.
> >>
> >>When I use the import command I set the name to "rec": import
> >>ascii rec=/home/chris/list.csv r=\n f=,
> >>
> >>Then to remove the carriage return I use: rc=xlate(rec(14),chr("13"),"")
> >>
> >>The number 14 inside rec(14) is the number of the field you are
> >>importing.  If every field has a carriage return in them you
> >>will need to use xlate for every field, rec(1), rec(2), and so
> >>on for the number of fields you are importing per record.  On
> >>Linux when I'm importing a CSV file from Windows I just need to
> >>run the xlate command on the last field I'm importing.
> >>
> >>-- Chris
> >>
> >>-----Original Message-----
> >>From: Mike Fedkiw via Filepro-list
> >>[mailto:filepro-list at lists.celestial.com]
> >>Sent: Friday, August 25, 2017 11:33 AM
> >>To: 0 Filepro List <filepro-list at lists.celestial.com>
> >>Subject: Importing/exporting data with carriage returns (I Think)
> >>
> >>win-server 2008 r2/filepro 5.0.09dn9
> >>
> >>Can someone tell me how or what I can do to import data into
> >>filepro that has carriage returns within the data cells?
> >>
> >>I receive these nice XLS files from my vendors with extended
> >>descriptions for things that I want to get into a memo fields in
> >>filepro but I'm having all sorts of issues trying to make that
> >>happen.
> >>
> >>Usually after setting up the XLS file to the way it needs to be
> >>for the import I'd save it as a DXF file. That's been working
> >>just fine for quite some time but when a cell contains returns I
> >>get an error message saying it's not a valid DXF file. I also
> >>tried saving it as a CSV file and importing that but the cells
> >>with the returns didn't import at all when I tried that. And I'm
> >>not even sure I'm saving it as the correct type of CSV(Comma
> >>delimited CSV or MS-DOS CSV) for importing it.
> >>
> >>Even if I get the import figured out if the data does have and
> >>returns within the memo it seems to stop exporting that fields
> >>data after the first one.
> >>
> >>If at all possible, I would really like to maintain the returns
> >>because it makes it much easier to read the data in the memo and
> >>it would also make the exported data much nicer too read with
> >>them included.
> >>
> >>AND...instead of me sitting here trying to figure this out for
> >>another week or so like I just did with all the MEMO stuff, I'd
> >>just assume pay someone to set it up for me. If someone is
> >>interested in doing that, let me know.
> >>
> >>
> >>
> >>Mike
> >>
> >>
> >>
> >>
> >>
> >>_______________________________________________
> >>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
> >
> >_______________________________________________
> >Filepro-list mailing list
> >Filepro-list at lists.celestial.com
> >Subscribe/Unsubscribe/Subscription Changes
> >http://mailman.celestial.com/mailman/listinfo/filepro-list
> >
> >
> >
> >
> >---
> >This email has been checked for viruses by AVG.
> >http://www.avg.com
> >
> >
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
> 

-- 
Audio panton, cogito singularis.