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
How Do I change the MTU (VMNIC0)on ESXI 4.0
CInt not working
How do I uninstall Advanced Mass Sebder?
Microsoft Access DSum over Multiple Criteria
DLookUp based on text box
Save unbound combobox column value in Access 2007
Freeze pane on Excel 2007 pivot table
MS ACCESS Color Picker
relationship type in Access
Table Connected via ODBC not showing newly added fields