Hi,
We use "spawn" command to open files from our runtimes. It works well for all Windows files (.doc, .docx, .txt, ...) except from .msg files for which we have this info : "The command line argument is invalid. check the switch you are using."
Is there a way to solve this problem ?
Thanks for advance.
Laurent.
------------------------------
Laurent MEROT
Proges Plus
Willems FR
------------------------------
Page 1 / 1
Hi,
We use "spawn" command to open files from our runtimes. It works well for all Windows files (.doc, .docx, .txt, ...) except from .msg files for which we have this info : "The command line argument is invalid. check the switch you are using."
Is there a way to solve this problem ?
Thanks for advance.
Laurent.
------------------------------
Laurent MEROT
Proges Plus
Willems FR
------------------------------
We use "spawn" command to open files from our runtimes. It works well for all Windows files (.doc, .docx, .txt, ...) except from .msg files for which we have this info : "The command line argument is invalid. check the switch you are using."
Is there a way to solve this problem ?
Thanks for advance.
Laurent.
------------------------------
Laurent MEROT
Proges Plus
Willems FR
------------------------------
The spawn command will try to determine the executable associated with a .msg file by calling the Windows function FindExecutable(), which returns something like (e.g.):
- "C:\\Program Files\\Microsoft Office\\root\\Office16\\OUTLOOK.EXE"
A very simple workaround for cases like this is to delegate the work to the Windows Command Prompt (cmd.exe). E.g.
- spawn("cmd /C myemail.msg")
That works fine but it leaves you with an ugly DOS box in the middle. You could get rid of this by using a signature with the implementation Operating System (OS) Command. E.g.
- activate "OSCMD".COMMAND("cmd /C myemail.msg")
Or another option would be to spawn a command like:
- spawn("outlook -f tmp.msg")
I hope this helps.
------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland
------------------------------
Hi Laurent,
The spawn command will try to determine the executable associated with a .msg file by calling the Windows function FindExecutable(), which returns something like (e.g.):
A very simple workaround for cases like this is to delegate the work to the Windows Command Prompt (cmd.exe). E.g.
That works fine but it leaves you with an ugly DOS box in the middle. You could get rid of this by using a signature with the implementation Operating System (OS) Command. E.g.
Or another option would be to spawn a command like:
I hope this helps.
------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland
------------------------------
The spawn command will try to determine the executable associated with a .msg file by calling the Windows function FindExecutable(), which returns something like (e.g.):
- "C:\\Program Files\\Microsoft Office\\root\\Office16\\OUTLOOK.EXE"
A very simple workaround for cases like this is to delegate the work to the Windows Command Prompt (cmd.exe). E.g.
- spawn("cmd /C myemail.msg")
That works fine but it leaves you with an ugly DOS box in the middle. You could get rid of this by using a signature with the implementation Operating System (OS) Command. E.g.
- activate "OSCMD".COMMAND("cmd /C myemail.msg")
Or another option would be to spawn a command like:
- spawn("outlook -f tmp.msg")
I hope this helps.
------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland
------------------------------
It works very weel as you described, thanks !
Regards,
Laurent.
------------------------------
Laurent MEROT
Proges Plus
Willems FR
------------------------------
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.