Re: probs executing own binaries in procedures

1st: Assuming that you can execute "myownapplication" from the shell - and it's in the path for whichever user is running the sp, then you need to check that it exits with a 0. Error -668 really means that your system command didn't exit with a 0. Which is not the same as "system command cannot be executed". The error message is wrong ( or at least confusing ), IMHO. The isam error gives you the exit-code. ie, all of these would give a -668 : : nosuchcommand : echo $? 127 : notexecutable : echo $? 126 : (exit1) echo $? 1 2nd: Just build you command and arguments into a string, eg. define l_command char(64); let l_command = "myownapplication " || myarg1 || " " || myarg2; system l_command; HTH >>> Martin Gentzsch <mgentzsch@lmp.de> 02/10/00 12:29pm >>> Hello ! I have a problem: Executing a procudure by a trigger passing = new tupel-values as parameters works well. But I=B4d like this procedure to make a "system"-call = of an external binary. Tests like = system "echo" = work but = system "myownapplication" in the procedure return = Error 668: system command cannot be executed the application lies in the path (/usr/bin) and has execution-permissions to others, user and group 2nd: How is the syntax to pass the arguments to myownapplication wich are passed to the procedure by the trigger ? Thanx a lot, Martin