invalid argument system runtime error on line with variable lookup

[GCC Consulting]

Bruce,

Check for a qualifier, if not use std lookup format.

If there is a qualifier, use the format I suggested.

If: qual = ""
Then: fileeq = filen
If: qual ne ""
Then: fileq = (filen&"@"&qual)

Richard Kreiss
GCC Consulting
  

> -----Original Message-----
> From: 
> filepro-list-bounces+gccconsulting=comcast.net at lists.celestial
> .com 
> [mailto:filepro-list-bounces+gccconsulting=comcast.net at lists.c
> elestial.com] On Behalf Of Bruce Easton
> Sent: Thursday, October 25, 2007 3:22 PM
> To: filepro list
> Subject: RE: invalid argument system runtime error on line 
> with variable lookup
> 
> Bruce Easton wrote Thursday, October 25, 2007 2:34 PM:
> > 
> > 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{""
> > > >> ----- -  -  -  -  -  -  -  -  -  -  -  -
> > > >
> > > > This line with qual blank should be giving you fileq = 'filen@'.
> > > > You are probably looking for fileq = 'filen' without 
> the @ symbol.
> > > > Some kind of conditional probably should be set to 
> prevent the '@'
> > > > symbol from being set when qual is blank or perhaps to add '""'
> > > > after the '@' symbol when qual is blank.
> > > [...]
> > > 
> > > A lookup to "filen@" and one to "filen" are not the same thing.
> > > 
> > > The former looks up to the non-qualified "filen" file, 
> whereas the 
> > > latter looks up to the current qualifier in the "filen" file.
> > > 
> > 
> > That was my understanding as well.  This particular program 
> is 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.
> > 
> > Bruce
> > 
> > Bruce Easton
> > STN, Inc.
> > 
> 
> When I use a static filename or a variable filename without 
> any qualifier nor "@" in the expression, dclerk(Win5.07) 
> stopped complaining there, and issued the same error for the 
> next place where I have the lookup formatted my original way.
> 
> So, it does seem to have a problem with variable named 
> lookups that are trying to accomodate possible qualifiers.  
> None of the suggested changes have made any difference.  I 
> even tried lookup alias = ((filen)@(qual))  r=rv -n thinking 
> it might see "@" in a better way if it was not a variable 
> part of the expression, but that did produce a syntax error.
> 
> Now I'm really starting to wonder if this is a Windows fp 
> thing or a 5.7 fp thing.
> 
> Bruce
> 
> Bruce Easton
> STN, Inc.
> 
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>