Error on system() in fP 5.0.14 Win32 - Need Help

[John Esak]

Hi,
Two things... First stupid....

You have a {hf  and are dcalling it the second path or the file you want to
store the data to... Then you would need it to be:

   <hf

The { will smash the whole path directly against the .pl and you wouldn't
have two paths, but one long one.  I'm guessing these are all just typoes.

Seconed thing.  The reason I always use "cmd" nistead of command in the
Windows Run Dialoog or when calling it from any process is that "cmd" will
allow you to CD (change directory) to a path that contains SPACES in it, and
"command" will not.  This is usually very important.

John
 

> -----Original Message-----
> From: filepro-list-bounces+john=valar.com at lists.celestial.com 
> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.co
m] On Behalf Of Fairlight
> Sent: Wednesday, September 01, 2010 8:50 PM
> To: 'filePro Mailing List'
> Subject: Re: Error on system() in fP 5.0.14 Win32 - Need Help
> 
> You'll never BELIEVE what Scott Walker said here...:
> > Thinking out loud.
> > 
> > What's the value of hf?
> 
> The value of hf is just the second path in the command...the 
> file I want
> the command to store the data to.
> 
> > Try a show of ut just before the system command to see that 
> it contains
> > everything you think it does.
> 
> It does.
> 
> I just found the problem, actually.
> 
> filePro's system() function apparently relies on Windows API 
> functionality
> that entirely ignores file extensions for running programs 
> like *.pl perl
> scripts.  So even if you associated .pl with the full path to 
> perl.exe, it
> won't run unless you supply the interpreter path first.
> 
> If you change this:
> 
> Then: ut="f:/filepro/cgi_control/utcstamp.pl"{hf
> 
> ...to this:
> 
> Then: ut="c:/perl/bin/perl.exe f:/filepro/cgi_control/utcstamp.pl"{hf
> 
> ...suddenly it works.
> 
> *sigh*  I'm annoyed, but at least I'm no longer hung up on 
> that mysterious
> crash.  The comspec terminology kept nagging at me--why 
> wasn't that valid?
> Because it's not a valid executable in its own right, it's 
> associated with
> an interpreter.
> 
> Thanks for the attempt to help, Scott!
> 
> Bests,
> 
> mark->
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>