Bad function number.

[Jose Lerebours]

A few things:

a. Clear event log before you try again
b. Try to run your program and check event log, this may show you the 
info Ken is looking for
c. Try to run program using dclerk instead of rclerk (think to recall 
cases where r* failed where d* did not)
d. Add -u to you command just in case your problem is due to record 
locking and bad error reporting  ;-)



On 09/22/2016 12:19 PM, Robert Repko via Filepro-list wrote:
> No, no additional information.  I copied and pasted the complete error.  I'll try it again just to make sure but I checked that the environment variable was set and then copied and pasted the error message at it appeared.  When I get back in the office I'll try it again and post the results.
>
> Robert T. Repko
> R² Consultants
>
> -----Original Message-----
> From: Kenneth Brody [mailto:kenbrody at spamcop.net]
> Sent: Thursday, September 22, 2016 11:08 AM
> To: Robert Repko; 'FilePro Mailing List' (filepro-list at lists.celestial.com)
> Subject: Re: Bad function number.
>
> On 9/21/2016 10:11 PM, Robert Repko via Filepro-list wrote:
>> Ken,
>>
>> Thanks for the reply.
>>
>> I set PFSHOWWINERROR=ON and ran the import again and receive the same error message, listed below.
>>
>> *** A System Error Has Occurred ***
>>
>> On File: c:\tmp\2016PAYROLL.csv
>>
>> Output Processing
>> Line Number: 2
>>
>> import ascii imp=c:\tmp\2016PAYROLL.csv r=\n f=, o=" c="
>> ^
>> Bad function number.
> [...]
>
> There's no additional info after that line?  Like "Last Windows error was ..."?
>