There are two problems in your code. The first one is the variable assignment
set InputFile ="C:\Temp\InputFile_mod.csv"
^
set outPutFile = "C:\Temp\outputFile.dat"
^ ^
The spaces indicated are included in the variable name (when placed in the left side of the equal) and in the value stored (right side of the equal)
It is a good habit to quote value assignment to prevent problems with special characters, but the recomended syntax is
set "InputFile=C:\Temp\InputFile_mod.csv"
set "outPutFile=C:\Temp\outputFile.dat"
where quotes protect the assignment, there are no spaces around the equal sign and note that, with this syntax, the quotes are not stored in the variable value.
The second problem is how you use the variables. Your vbscript code does not expect two variable names, but two file names. So, you don't have to pass the variable names, but the values stored inside them. In batch files this is done using %varname%.
set "InputFile=C:\Temp\InputFile_mod.csv"
set "outPutFile=C:\Temp\outputFile.dat"
cscript SFEVBMacro.vbs "%InputFile%" "%outPutFile%"
The batch parser will replace the variable read operation with the value inside the variable and then execute the command.
If you prefer to pass the variable names (your original code) instead of the variable values, you can do it, but then your vbscript should be changed to retrieve the variables contents
With WScript.CreateObject("WScript.Shell").Environment("PROCESS")
inputFile = .Item( WScript.Arguments.Unnamed(0) )
createdFilePath = .Item( WScript.Arguments.Unnamed(1) )
End With
As the code receives environment variable names, we need to use the Environment property of a WScript.Shell instance to retrieve the variable contents from the process environment.
=sign in thesetcommand lines as they become part of the variable names and values otherwise... when expanding (reading) variables you need to put its name in between a pair of%signs...