Bad function number.

[Fairlight]

Offhand, the only thing I can think of is, "Is that a literal colon in the
path to the file, or do you properly have a ^A in place, there?"

m->

On Wed, Sep 21, 2016 at 09:42:44PM +0000, Robert Repko via Filepro-list thus spoke:
> 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
> 

-- 
Audio panton, cogito singularis.