import processing must us .wp extension

Kenneth Brody kenbrody at bestweb.net
Tue Feb 8 06:47:21 PST 2005


"Jean-Pierre A. Radley" wrote:
> 
> 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?

No.  My guess is he had "file" (the one he wanted to import) and "file.wp"
(something left over from a different import), so filePro tried to import
the "file.wp" file, which didn't match what he thought it was.  He then
"added the .wp extension" through some unspecified means (copied it, had
the other program regenerate it with the ".wp", renamed it, ...) and then
had filePro do the import again.  This time, when filePro imported the
"file.wp" file, it matched his processing's expectations, and "worked".

-- 
+-------------------------+--------------------+-----------------------------+
| Kenneth J. Brody        | www.hvcomputer.com |                             |
| kenbrody/at\spamcop.net | www.fptech.com     | #include <std_disclaimer.h> |
+-------------------------+--------------------+-----------------------------+
Don't e-mail me at: <mailto:ThisIsASpamTrap at gmail.com>




More information about the Filepro-list mailing list