invalid argument system runtime error on line with variable lookup
Kenneth Brody
kenbrody at bestweb.net
Thu Oct 25 12:41:43 PDT 2007
Quoting Bruce Easton (Thu, 25 Oct 2007 14:34:29 -0400):
> Kenneth Brody wrote Thursday, October 25, 2007 2:17 PM:
>>
>> Quoting Bill Akers (Thu, 25 Oct 2007 12:33:08 -0500):
>>
>> > Bruce Easton wrote:
>> >> I'm getting a filepro runtime error:
>> >>
>> >> *** A System Error has occurred ***
>> >> on file: \dvr/filepro/DEUDAS/map
>> >> Line: 1407 invalid argument
>> >>
>> >> from an rclerk process (Windows fp ver. 5.07)
>> >>
>> >> where line 1406 and 1407 in the processing are:
>> >>
>> >> If:
>> >> Then: fileq = filen{"@"{qual{""
>> >> ----- - - - - - - - - - - - -
[...]
> never called (from my scripts lines) with a qualifier (against the
> file that I am running from), therefore, in my variable named
> lookup expression, I intentionally use the "@" after the filename
> expression, and *sometimes* append a qualifier to it (for the
> file that I am lookup up to).
>
> This has worked fine under Unix with fp5.14.
>
> Also, if this is the problem, then wouldn't clerk at least
> wait until the program got to the line to evaluate the lookup
> before coming up with a system error? I didn't get a syntax
> error for it.
If it's giving you a filename along with the line number, then it has
executed processing and has reached that line. It's not possible for
it to be giving you the correct lookup name without processing having
been executed, and the filename calculated at runtime.
I do note that your original message says "rclerk", which of course
has no debugger. I assume you ran dclerk when you tried to debug it.
Put a "DEBUG ON" just before the lookup and try it again.
--
KenBrody at BestWeb dot net spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com
More information about the Filepro-list
mailing list