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 <b...@twft.com> 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 > > rdim...@evergreeninfo.net > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
