We have MAS200: 2 clients and a server.
A batch file on Client_1 works perfectly to run an import job on the server:
cd "P:\BEST\MAS90\HOME"
"P:\BEST\MAS90\HOME\PVXWIN32.EXE" ..\LAUNCHER\SOTA.INI ..\SOA\MAS90 -ARG VIWI07 W 0 DIRECT DISPLAY KTU"
This imports invoices into AR7 and AR8 from a SQL Server table. WORKS GREAT.
PROBLEM:
On Client_2, the same batch file appears to run correctly; the DOS window pops up and displays the lines being executed. No errors are indicated in the DOS window, and there is no error feedback from pxvwin32.
BUT.........the data does not make it into AR7 and AR8 when the batch file is run on Client_2. It simply is not there.
Other facts:
--The drive letter P is set up exactly the same on both clients.
--The import job can be run successfully on both clients using the MAS VI module.
Any ideas? IS it Windows file permissions?
Client_1, which works, is Windows 98. Client_2 is Windows 2000 Server.
Thanks,
Scott Murray
A batch file on Client_1 works perfectly to run an import job on the server:
cd "P:\BEST\MAS90\HOME"
"P:\BEST\MAS90\HOME\PVXWIN32.EXE" ..\LAUNCHER\SOTA.INI ..\SOA\MAS90 -ARG VIWI07 W 0 DIRECT DISPLAY KTU"
This imports invoices into AR7 and AR8 from a SQL Server table. WORKS GREAT.
PROBLEM:
On Client_2, the same batch file appears to run correctly; the DOS window pops up and displays the lines being executed. No errors are indicated in the DOS window, and there is no error feedback from pxvwin32.
BUT.........the data does not make it into AR7 and AR8 when the batch file is run on Client_2. It simply is not there.
Other facts:
--The drive letter P is set up exactly the same on both clients.
--The import job can be run successfully on both clients using the MAS VI module.
Any ideas? IS it Windows file permissions?
Client_1, which works, is Windows 98. Client_2 is Windows 2000 Server.
Thanks,
Scott Murray