Tip of the day - Failed IMPORT (SOLVED)

[Lerebours, Jose]

Jeff suggested:

[ snip ]
> 
> Right.  The import command is limited in that you
> can't have a variable as a separator.  You may want to
> consider using the raw read commands and parsing the
> information yourself.
> 

It turns out that I have a shell script that takes a 
text file and it produces a nice columnar file (nicely
aligned columns - fixed lengths).

The script syntax is:

nicecol -i IFS -o OFS [source.file.name] > [output.file.name]

NOTE: You can find the script on this link
http://www.shelldorado.com/scripts/cmds/nicecol


So, since I can now identify what my user uses as a field
separator and I can convert that to whatever I want, I
simply added 'nicecol' to my filePro routine to convert
to a separator I can use and not worry about it.

Check above link and find, as I did, tons of very nice 
scripts - including one that allow you to take a plain
text report and convert it into HTML right off your
filePro application.

Regards;


Jose Lerebours


PS:  I modified my version of the script to look at all
columns as "string" so that I do not loose padding zeros.