importing extended descriptions from excel

[Mike]

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







On 8/10/2017 10:34 AM, Richard Kreiss via Filepro-list wrote:
> filePro manual:
>
> Increase default record length for importing ASCII files. Default "1024"
> prior to release 5.6.0 and "10000" with 5.6.0 and later. (*clerk, *report)
>
>
>
> Richard Kreiss
> GCC Consulting
>
>
>
>
>> -----Original Message-----
>> From: Filepro-list [mailto:filepro-list-
>> bounces+rkreiss=verizon.net at lists.celestial.com] On Behalf Of Mike
> Schwartz
>> via Filepro-list
>> Sent: Thursday, August 10, 2017 8:22 AM
>> To: 'Filepro List' <filepro-list at celestial.com>
>> Subject: RE: importing extended descriptions from excel
>>
>>> On 8/9/2017 10:28 PM, Mike Schwartz wrote:
>>>>> Can someone please help me out or at least point me in the right
>>>> direction?
>>>>> I have an excel files from my vendors which I usually use for
>>>>> importing in price increases and other small modifications but now
>>>>> I'd like to import extended descriptions into Filepro too. When I
>>>>> tried using a memo field
>>>> for
>>>>> that data I got a critical error which forced Filepro to close.
>>>> [Snip]
>>>>> Thank You, Mike
>>>>         You didn't mention which version of filePro you or on, nor
>>>> your operating system, but check the size of your PFIMPBUF
>>>> environmental variable.  By default I think PFIMPBUF is set fairly
>>>> small, like 1024 characters.  This means filePro will truncate any
>>>> "import" records to a maximum length of 1024 characters.  Increase
>>>> PFIMPBUF large enough to handle the longest incoming record you expect
> in
>> your .DIF files.
>>>> Mike Schwartz
>>>>> I'm running server 2008 R2 and Filepro 5.09dn9
>>> I looked in the Filepro dir using F6 and also in the startup batch
>>> file and I didn't see PFIMPBUF set anywhere. In that case can I just
>>> set it to whatever I want?
>>>
>>>
>>> Mike
>>>
>>          I don't recall what the maximum length is for PFIMPBUF, nor if it
> applies to
>> the Windows version of filePro.  You would have to look that info up in
> your
>> filePro manuals, or I believe Stuart Werner's filepro Bible could probably
> help.  (I
>> am not in my office yet and don't have a copy of either available to me
> right
>> now...)
>>
>>         If this is the problem, as I recall, what you would see is the
> first several fields
>> getting imported OK, but none of the fields past 1024 characters in the
> record
>> would get imported.
>>
>>         I've written hundreds (perhaps thousands) of imports in filePro,
> mostly for a
>> mail order customer I had up to a few years ago, and on their Unix server
> I think
>> I had PFIMPBUF set to something like 32000.  As I recall, that might have
> been
>> the max.
>>
>>         I wrote a few imports for an insurance company using the DOS
> version of
>> filePro many years ago.  It seems like there was something I had to set to
> get
>> the DOS version working, but I don't recall what it was.  I've written a
> few
>> imports using the Windows version of filePro, but I don't recall if I set
> PFIMPBUF
>> or did something else, or if the files I was importing were small enough
> that I
>> didn't have to worry about it.  Most of the importing I've done involves
> mailing
>> lists that have records that are shorter than 1024 characters.
>>
>> Hope that helps!
>>
>> 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