import processing must us .wp extension

[Kenneth Brody]

Quoting Dennis Malen <dmalen at malen.com>:

> No, I only had one file which was reading the 4th field and not the
> first.
> Adding ".wp" fixed it.
[...]

filePro doesn't care about filename extensions, and will import the
file exactly the same way regardless if it's called "myfile" or
"myfile.wp".  If changing the extension changed the way that the
import happened, then something else was going on.  If you told
filePro to import "/tmp/myfile", and did not have PFADDWP=OFF set,
then filePro really imported "/tmp/myfile.wp".  If that file did
not exist, you would have gotten a "file not found" error.

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com