import processing must us .wp extension

[Dennis Malen]

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

Dennis
----- Original Message ----- 
From: "Jean-Pierre A. Radley" <appl at jpr.com>
To: "FilePro Mailing List" <filepro-list at lists.celestial.com>
Sent: Monday, February 07, 2005 9:41 PM
Subject: Re: import processing must us .wp extension


> Ken Brody propounded (on Mon, Feb 07, 2005 at 06:58:45PM -0500):
> | Dennis Malen wrote:
> | >
> | > I had an unusual experience with import processing.
> | >
> | > The target file was created as a tab delimited file.
> | >
> | > When I commenced my processing to import the information and pulled 
> the
> | > value of  the first field from the import processing, the value of the 
> first
> | > field was the value of what the 4th field was. Every value was four 
> fields
> | > off.
> | >
> | > I added the .wp extension to the target file and it worked fine.
> | >
> | > I don't know if that is a bug in 4.8 or not??
> |
> | My guess is you already had a file with the same name, but with the 
> ".wp"
> | extension, and filePro was reading that one.
>
> Huh?  So he had file.wp and file, then "added the .wp extension to the
> target file" and had TWO file.wp?  In the same directory?
>
> -- 
> JP
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>
>