Jack, Thanks, that resolved the memory error (for now anyway). However, now I am get no standard output from the call. I assume that an easy work around would be to pipe to to a file, then read that. Not the most efficient, but should work.
I suppose the calling of a new command.com somehow nukes that link. Brian
