Screen ghost??

[ivan]

--- On Wed, 1/6/10, Richard Kreiss <rkreiss at verizon.net> wrote:

> From: Richard Kreiss <rkreiss at verizon.net>
> Subject: RE: Screen ghost??
> To: "'Kenneth Brody'" <kenbrody at spamcop.net>
> Cc: "'filepro'" <filepro-list at lists.celestial.com>
> Date: Wednesday, January 6, 2010, 11:36 AM
> 
> 
> > -----Original Message-----
> > From: Kenneth Brody [mailto:kenbrody at spamcop.net]
> > Sent: Tuesday, January 05, 2010 10:54 PM
> > To: Richard Kreiss
> > Cc: 'filepro'
> > Subject: Re: Screen ghost??
> > 
> > On 1/5/2010 5:32 PM, Richard Kreiss wrote:
> > [...]
> > >> Here is the system call we use:
> > >>
> > >> system "$PFPROG/fp/dclerk fesequip -sadd -lx
> -xa -d -t 130000 -r
> > > \""&pm{"\" -h
> > >> 'EQUIPMENT FILE'  "
> > >
> > > Try this for you system call:
> > >
> > > sy=" fesequip -sadd -lx -xa -d -t 130000 -r
> "<pm<" -h EQUIPMENT FILE"{""
> > >
> > > System "$PFPROG/fp/dclerk"<sy
> > >
> > > Not sure if this will work under *nix. However, I
> have found that fp
> running
> > > on windows does not need the " marks.
> > [...]
> > 
> > You absolutely need quotes around any parameter that
> contains "special"
> > characters, such as spaces.  (Or quote the
> "special" characters
> themselves.)
> > 
> > This won't work on any platform:
> > 
> >      dclerk foo -h EQUIPMENT FILE
> > 
> > It must be:
> > 
> >      dclerk foo -h "EQUIPMENT FILE"
> > 
> > or something equivalent.
> > 
> > --
> > Kenneth Brody
> 
> Ken,
> 
> Did not want to reply until I test this.
> 
> Hd="Equipment File"
> 
> sy=" foobar -sadd -lx -xa -d -t 130000 -r "<pm<"
> -h"<hd{""
> 
> System "$PFPROG/fp/dclerk"<sy
> 
> I test this on my system and what happened is the -h option
> only showed the
> first word which is probably as would be expected if not
> quotes are used.
> 
> Richard
> 
> 
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
> 
OK, so I have been experimenting with some things and I added an @key statement that triggered my original system call.  It works like a charm.  So I'm guessing that something in my code leading up to my original call is causing the error. 

It doesn't seem to be a lookup though, and I would think the close comment would take care of any of that.  Does anyone have any suggestions as to what else it could be?

-Ivan