Try this UDF modification to the end if the file to test it:
Code:
; don't run the command
;Shell '%COMSPEC% /e:1024 /c '+$shellcmd+' >NUL 2>NUL'
$ = RedirectOutput('jtcmd.bat')
$shellcmd ?
$ = RedirectOutput('')
This will place the complete JT command syntax into a BAT file that you can edit. Edit the file and review the syntax, making sure that commands don't run together (have proper spaces between them), are all on one line (turn line-wrap OFF), and maybe even review the syntax for correctness. If you download the zip file for my tsControl library, there's a JT doc file that better describes the functions and arguments of JT.
Finally, after validating the bat file, execute it and see if any other errors are reported. There may be a "JT.exe is not a recognized command" if it can't find the file. You may see other errors from JT.
This process will help you isolate whether the UDF is not functioning, if it is not properly generating JT syntax, or JT itself is failing. The UDF has been well tested, so - other than your (supposedly) minor modification, the only other errors could be introduced when you downloaded it. Some spaces may not be present, affecting the JT syntax generation or something similar. Until you can begin to narrow it down, you're shooting in the dark.
Glenn
_________________________
Actually I
am a Rocket Scientist!
