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 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 works. > > Pretty clear LC is messing with the command before it hands it off to the > shell. > > Pete > lcSQL Software <http://www.lcsql.com> > > > > On Tue, Oct 16, 2012 at 2:37 PM, Bob Sneidar <[email protected]> wrote: > >> 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 16, 2012, at 2:27 PM, Peter Haworth wrote: >> >>> 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 Windows command prompt. >>> Pete >>> lcSQL Software <http://www.lcsql.com> >>> >>> >>> >>> On Tue, Oct 16, 2012 at 2:00 PM, Bob Sneidar <[email protected]> wrote: >>> >>>> 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 outside a >>>> quoted string. >>>> >>>> It's my understanding that the command should work in the command prompt >>>> without quotes, but there must be something about the shell() function >>>> itself that messes with the command. >>>> >>>> Bob >>>> >>>> >>>> On Oct 16, 2012, at 12:01 PM, Ralph DiMola wrote: >>>> >>>>> Peter, >>>>> >>>>> Lose the quotes around the program name and you should be OK >>>>> >>>>> Ralph DiMola >>>>> IT Director >>>>> Evergreen Information Services >>>>> [email protected] >>>> >>>> >>>> _______________________________________________ >>>> use-livecode mailing list >>>> [email protected] >>>> Please visit this url to subscribe, unsubscribe and manage your >>>> subscription preferences: >>>> http://lists.runrev.com/mailman/listinfo/use-livecode >>>> >>> _______________________________________________ >>> use-livecode mailing list >>> [email protected] >>> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >>> http://lists.runrev.com/mailman/listinfo/use-livecode >> >> >> _______________________________________________ >> use-livecode mailing list >> [email protected] >> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode >> > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
