Microsoft
Software
Hardware
Network
Question : Am trying to get a MAS90 VI Job to run from WinExec(). Runs fine from command prompt, but not from WinExec().
Dear Sirs,
I am able to get the following MAS90 VI job to run from the command prompt
"C:\Program Files\Sage Software\MAS 90\Version4\MAS90\Home\pvx
win32.exe"
..\launcher\sota.ini "C:\Program Files\Sage Software\MAS 90\Version4\MAS90\SOA\star
tup.m4p" -ARG DIRECT UIOFF "" "" 'SYN' 'VIWX00' 'AUTO'
However, when I try to run it from WinExec(), it does not run the file.
int result=WinExec("\"C:\\Prog
ram Files\\Sage Software\\MAS 90\\Version4\\MAS90\\Home\
\pvxwin32.
exe\" \"C:\\Program Files\\Sage Software\\MAS 90\\Version4\\MAS90\\Launc
her\\SOTA.
INI\" \"c:\\Program Files\\Sage Software\\MAS 90\\Version4\\MAS90\\SOA\\
startup.m4
p\" '-ARG' 'DIRECT' 'UIOFF' \"\" \"\" SYN 'c:\\Program Files\\Sage Software\\MAS 90\\Version4\\MAS90\\VI\\V
IWX00' 'AUTO'", 1);
It returns code 33.
Any ideas??
Best, Brett G.
Answer : Am trying to get a MAS90 VI Job to run from WinExec(). Runs fine from command prompt, but not from WinExec().
BTW, try "FileMon" (
http://technet.microsoft.
com/en-us/
sysinterna
ls/
bb89664
2.aspx
) to see which file cannot be found or accessed.
Random Solutions
sp_addlinkedserver using SQL Authentication
Move smtp cdo message to a file
sql : mm-yy from date time stamp
two servers on one internet connection
How to create Access Check Box Pick List Form
Union Query duplicates
Verification Process
Cannot disable hibernation in Vista
If there are multiple inf files on the computer which have the same VID/PID as your device, how does windows choose which driver to use?
Unrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive