Thanks Mike, didn't know about the LC shortfilepath function.
Pete
lcSQL Software http://www.lcsql.com
On Tue, Oct 16, 2012 at 5:54 PM, Mike Bonner bonnm...@gmail.com wrote:
When you put the contents into your tCommand variable you can do this
put shortfilepath(the file path with spaces)
Hey that's a great tip Mike!
Bob
On Oct 16, 2012, at 5:54 PM, Mike Bonner wrote:
When you put the contents into your tCommand variable you can do this
put shortfilepath(the file path with spaces) the paramers and
switches to pass into tCommand
At this point no quotes are needed
I have a variable tCommand whose contents are:
C:\Program Files (x86)\GnuWin32\bin\diff.exe other stuff
To clarify, the quote chars are in tCommand
If I execute it with
put shell(tCommand) into temp
... temp contains 'C:\Program' is not recognized as an internal or
external command
If I
16, 2012 2:57 PM
To: How to use LiveCode
Subject: Shell command problem on Windows 7
I have a variable tCommand whose contents are:
C:\Program Files (x86)\GnuWin32\bin\diff.exe other stuff
To clarify, the quote chars are in tCommand
If I execute it with
put shell(tCommand) into temp
I tried this:
on mouseUp pMouseBtnNo
put quote C:\Program Files\Adobe\Reader 9.0\Reader\AcroRD32.exe quote
into tCommand
put shell(tCommand) into tResult
answer tResult
end mouseUp
I saved a windows standalone and copied it to my XP VM. I don't use Vista or 7.
It launches
I tried that Ralph and it wouldn't work. I got the same result Peter did when I
excluded the quotes. Another way to do it is shell(quote tCommand quote)
That way you can be sure there are quotes when the command is shelled out. This
would work only if you don't have arguments that must be
I have an update on this problem.
The other stuff mentioned as part of the command line in my original
message includes a file path. Initially, I did not have quotes around the
file path but if the file path contained a space, I got an error. I then
put quotes around the file path parameter and
Bob,
My latest post explains more about this - it's not the program
name itself that causes the problem - it's the fact that
I'm passing parameters into the program on the command line enclosed in
quotes - that's what causes the error despite the fact that exactly the
same command works at a
I'm at a loss then without the app that you are testing. I'd have to see the
whole command with arguments and have the app installed to make any
determinations. Years of troubleshooting has taught me to reproduce the user's
issue before proceeding, and I can't do that here. Sorry.
Bob
On Oct
This is not an app problem Bob, the program never runs.
In any case, I've found a workaround for the problem, which is to issue two
commands in one call to the shell. So tCommand now contains:
cd C:\Program Files (x86)\GnuWin32\bin diff.exe -i-E -b -B path to
filename1 path to filename2
That
I mean diff.exe. I would need that to try the exact arguments you are using.
But glad you got it working.
Bob
On Oct 16, 2012, at 2:55 PM, Peter Haworth wrote:
This is not an app problem Bob, the program never runs.
In any case, I've found a workaround for the problem, which is to issue
When you put the contents into your tCommand variable you can do this
put shortfilepath(the file path with spaces) the paramers and
switches to pass into tCommand
At this point no quotes are needed around the filepath because there will
be no spaces. (it will be in 8.3 format)
On Tue, Oct 16,
12 matches
Mail list logo
