Send Event to open vbscript file with parameter

[kevinincontrol]

I can't get the Send Event with calculation to work as I want.

Send Event ["aevt"; "odoc"; "cmd.exe " & "c:/mytopdir/mydir/myscript.vbs " & $myvar] opens the cmd window to "C:\Program Files (x86)\FileMaker\FileMaker Pro 9\Extensions\xDBC Support\logging" and stops.

How can I get it to execute the script with the open arg? Is it possible?

Dozens of views, but no replies.  Is this something that is even possible to do?

Edited July 2, 2021 by kevinincontrol

[kevinincontrol]

70+ views, but no replies.  Did I post this in the wrong place?

[Josh Ormond]

What version of FileMaker are we talking about here?

Your profile says '11 Advanced', your question references "FileMaker Pro 9".

Either of those versions are really old... that may be the reason. Also keep in mind that sometimes ( a lot of the time ) the syntax of the commands are case-sensitive. Make sure that is correct.

Next:

1. If you paste the text of the command you are trying to run in the command line, does it work? Ultimately, FileMaker just hands off the command to the operating system, so there is not a lot of complexity in that leg of the action.
2. Can you give us a sample of what the argument looks like?
3. What are you expecting the action to do? You mention the path of the script to run, and you mention what shows up in the cmd window, but don't tell us if that is right, wrong, or no related.

[kevinincontrol]

Thanks for your reply. I appreciate you looking at this.

I would have chosen version 9 pro, but it is not available in the dropdown list, so I chose the closest one. I know it's an old version, but it's what I have to work with for now. Sorry for that.

The Send Event issue is this: when I type directly in the command line, all works well.

But using the send event, the command line contains "$myvar" rather than the value of $myvar (for example "2020-001").  I'm doing this using the Text option rather than the File or Calculation option for the command. So the command line sees:  "cmd.exe c:/mytopdir/mydir/myscript.vbs $myvar" rather than  "cmd.exe c:/mytopdir/mydir/myscript.vbs 2020-001".

Does this help clarify the issue?