importing extended descriptions from excel

Mike Schwartz mschw at athenet.net
Thu Aug 10 13:38:30 PDT 2017


> 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


  



More information about the Filepro-list mailing list