import processing must us .wp extension

[Dennis Malen]

Ken,

That was probably what happened. It probably read the other ".wp" file I 
had. Then when I copied over it and changed it to ".wp" it worked.

Can you clarify? If I had a file that did not have ".wp" appended and I 
requested an import from that file without the ".wp" I'm assuming it would 
work. It was only because I had two files named the same and one had the 
extension that the problem arose.

Dennis
----- Original Message ----- 
From: "Kenneth Brody" <kenbrody at bestweb.net>
To: "Dennis Malen" <dmalen at malen.com>
Cc: "Jean-Pierre A. Radley" <appl at jpr.com>; "FilePro Mailing List" 
<filepro-list at lists.celestial.com>
Sent: Tuesday, February 08, 2005 12:24 PM
Subject: Re: import processing must us .wp extension


> 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
>
>
>