CompuServe Messages

Sounds like you have a reasonable challenge to tackle. It is always amazing that people actually expect your code to work under the strangest of circumstances. (Who would have ever thought of a short line…) I have also been working on interfacing executables to applications through AREXX (specifically Turbotext) and I have found the same type of limitation that you have hit – there really isn't a good way to get an application run without having to go through the 'ADDRESS COMMAND' capability of AREXX. This of course leaves you without the ability to get any reasonable results from the program. (Bill, feel free to jump in any time here). One thing that I had looked at was creating a rexx function host that sits in the background to process messages and allow the application to get the options results.