importing extended descriptions from excel

[Brian K. White]

"import word" does csv files,
or you can also do them with plain import ascii

import word csv="file.csv"

import ascii csv="file.csv" r=\n f=, o=" c="

But I see no reason why your existing dif import shouldn't work.
I would suspect a record delimiter problem or some other data formatting 
or contents problem in the dif file.

-- 
bkw


On 8/10/2017 7:20 PM, Mike via Filepro-list wrote:
> I just increased the PFIMPBUF to 9600but that made zero difference as
> far as importing any more that the first eight columns of information.
>
> After that I tried changing the field lengths and formats on the first
> ten fields to (1,*), then I just put a single letter in each of the
> first ten columns of the dif file. When I tried importing that I got a
> "create process () failed 1812(0x00000714).
>
> That error went away of course once I limited the dif file to only eight
> columns of information. If there's limitations on how many columns of
> information you're able to import from a dif file I've never seen it.
>
> Someone mentioned that they use csv files but that's not even listed as
> an option in the help file under import, can someone help me with that?
>
> Mike
>
> Server 2008 R2, Filepro 5.0.09 DN9
>
>
>
>
>
>
>
>
>
> On 8/10/2017 4:38 PM, Mike Schwartz via Filepro-list wrote:
>>> After some testing, at least to me it looks like the PFIMPBUF is
>>> directly
>>> related to the individual fields valid length when importing but doesn't
>> seem
>>> to effect how many fields/columns I'm able to import.
>>>
>>> without setting PFIMPBUF I was able to import exactly 508 characters
>>> without getting this error.
>>>
>>> ========================================
>>>
>>> *** A filePro Error Has Occurred ***
>>>
>>> On File: /import/import.dif
>>>
>>> Input Processing
>>> Line Number: 9
>>>
>>> import DIF imp = (1)
>>> ^
>>> Bad Import Format.
>>> Not a valid DIF file.
>>>
>>> ==========================================
>>>
>>> After that I decided to see exactly what PFIMPBUF needed to be set to to
>>> import 999 characters without getting that error. It turned out to be
>>> PFIMPBUF=2006, PFIMPBUF=2005 got the error above.
>>>
>>> Anyway, I just set it to 2400 because the field length I'm using is
>>> 999 so
>> at
>>> least that part's solved but I'm still only to import the first eight
>> columns of
>>> the DIF file for some reason, everything beyond that is just blank, I
>> don't get
>>> it?
>>>
>>>
>>> Mike
>>>
>>> Server 2008 R2, Filepro 5.0.09 DN9
>>        I'm pretty sure PFIMPBUF is related to the record length; not
>> just the
>> length of one field.  However, with .DIF files, I don't know what the
>> record
>> delimiters are.  IE, I don't know if each field in a .DIF file is
>> considered
>> one record when filePro imports it.
>>
>>       I still think 2006 is the length of one full record that you are
>> importing and has nothing to do with the 999 characters.  There isn't any
>> reason not to set PFIMPBUF to some much larger number, like 9000, then
>> see
>> if that fixes your problem.
>>
>>        The symptom you are describing (only importing the first eight
>> fields)
>> probably means that PFIMPBUF needs to be set a LOT larger than it
>> currently
>> is.
>>
>> Mike Schwartz
>>
>>
>>
>> _______________________________________________
>> Filepro-list mailing list
>> Filepro-list at lists.celestial.com
>> Subscribe/Unsubscribe/Subscription Changes
>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>