FW: errors within an exported .slk file
Walter D Vaughan Jr
wvaughan at steelerubber.com
Mon Jul 21 06:03:50 PDT 2014
Sorry for the double post KB :(
-----Original Message-----
From: Walter D Vaughan Jr [mailto:wvaughan at steelerubber.com]
Sent: Monday, July 21, 2014 9:02 AM
To: 'Kenneth Brody'
Subject: RE: errors within an exported .slk file
> -----Original Message-----
> From: Kenneth Brody [mailto:kenbrody at spamcop.net]
> Sent: Monday, July 21, 2014 8:55 AM
> To: Walter D Vaughan Jr; filePro Mailing List
> Subject: Re: errors within an exported .slk file
>
> On 7/20/2014 6:15 PM, Walter D Vaughan Jr wrote:
> > As a single character delimiter we've used either a tilde ~ or the
> > pipe | Works 99% of the time.
>
> Why not tab? ("f=\t")
>
[Walter D Vaughan Jr]
Mostly because it's not a visual thing in most UI experiences when you are
eyeballing the data before importing, but I do bow down and recognize that
the tab character should have been first in my list of delimiters. Hail
"Tab" key. All Hail "Tab"
> [...]
> >> Actually a CSV file is where I started with a different export but
> >> I just couldn't get it to work because of asterisks, commas and
> >> semicolons within the field I wanted to export. That's why I went
> >> to the SLK file, it didn't care about
> [...]
>
> --
> Kenneth Brody
More information about the Filepro-list
mailing list