Non-blocking way to open MS Word files?

[xbury.cs at clearstream.com]

Just in case it might help...

if you use the shell() function to launch a process, you will be blocked.
If you dont want to be blocked, use "start" to have the shell launch the 
process and liberate your shell.

Start /? =
START ["title"] [/Dpath] [/I] [/MIN] [/MAX] [/SEPARATE | /SHARED]
      [/LOW | /NORMAL | /HIGH | /REALTIME] [/WAIT] [/B] [command/program] 
[parameters]
+++

Using MIN it will be minimized. 

On 30/01/2004 10:03:48 use-revolution-bounces wrote:
>--- Dave Beck <davethebrv at crystalpiersw.com> wrote:
>>
>> Hey,
>>
>> I sent this message to the list a while back but
>> never got a response. I'm
>> hoping this time I'll fair better. I still haven't
>> been able to come up with
>> a solution on my own.
>>
>> I'm writing a Windows app with Rev and need a way to
>> open files with MS Word
>> from a script in my app. I've been using the shell
>> command with the
>> parameter as the long path name of the file to
>> launch Word and open the
>> file. This which works well except that it is
>> blocking, meaning that my Rev
>> stack does not respond to mouse clicks etc. until
>> the user quits the MS Word
>> instance that was launched from my script!
>>
>> Does anybody know a way around this??
>>
>> Any help would be greatly appreciated.
>>
>> Thanks in advance,
>> Dave
>>
>
>Hi Dave,
>
>Do you get the same problem if you open the Word doc
>by means of the 'launch' command ?

Visit us at http://www.clearstream.com
                                                          
IMPORTANT MESSAGE

Internet communications are not secure and therefore Clearstream International does not accept legal responsibility for the contents of this message.

The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any views expressed in this e-mail are those of the individual sender, except where the sender specifically states them to be the views of Clearstream International or of any of its affiliates or subsidiaries.

END OF DISCLAIMER