Bad function number.

[Nancy Palmquist]

I did not get to the end of the stream but did you try using a different 
name for the "imp" part of the import.

See if you are fighting with a reserved word or function in filepro.

Always worth a try.

Nancy

On 9/21/2016 5:42 PM, Robert Repko via Filepro-list wrote:
> I have an import routine that I have used before but now I am getting a 'Bad function number' error when I try to import data.
> The file I am trying to import is a comma delimited ascii file.  It resides on c:\tmp and is called 2016payroll.csv
> My processing table is:
>
> nxtimp:::
> ::import ascii imp=c:\tmp\2016payroll.csv r=\n f=, o=" c=":
> :not imp:end:
> ::lookup irs = 1099  r=free  -n:
> ::irs(11)=imp(2):
> ::irs(12)=imp(1):
> ::write irs
> ::goto nxtimp
> The complete error is:
> *** 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.
>
> I don't see the problem.  Might I add that I am trying to import on a Windows 10 system (maybe that's my problem)
> Does anyone see what I am missing?
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>

-- 
Nancy Palmquist         MOS & filePro Training Available
Virtual Software Systems    Web Based Training and Consulting
PHONE: (412) 835-9417           Web site:  http://www.vss3.com