import

[GCC Consulting]

-----Original Message-----
From: filepro-list-bounces+gccconsulting=comcast.net at lists.celestial.com
[mailto:filepro-list-bounces+gccconsulting=comcast.net at lists.celestial.com]
On Behalf Of Steven Waters
Sent: Tuesday, January 10, 2006 9:46 AM
To: 'Filepro List'
Subject: RE: import

 

Quoting Jeff Harrison (Mon, 9 Jan 2006 14:34:03 -0800 (PST)):
[...]
> Sorry, I thought that I had done that in the past, but I guess I was 
> confusing it with export ascii.  At any rate you should be able to 
> specify "r=\n f=~" (or something else for the field separator that you 
> know is not in the data)

I believe that "f=255" works "best" for this.


I did f=255 and still only get the first record imported.
Is there a way to tell excel when saving as csv not to use commas but to use
"~"? Or when in the txt file add the ~ separator?
Here is one line of my data. I am still trying the alien file suggestion.

30210                        300 Cu-in. Brake Sys Accumulator
32     32-40-01   Landing Gear                                           737
EFS Aerospace, Inc.

If you continue to have a problem, save the file as a DBF and use dbcopy.
Check the data in the new file and the post it to your file.  If you need to
manipulate the data in any way, this will allow you to do it easily before
it is posted to your working file.

I built a library routine that checks for dbf files, displays the name in a
list box thereby allowing the user to select which file to "import".  A
system command runs dbcopy with the input dbf file name and the filePro file
which hold the data prior to posting to the working file.  

In this particular case, the dbf file structure is always the same.  I still
have to do a date conversion.

Just a thought on another way to get your data in.

Richard Kreiss
GCC Consulting