Problem running a perform logic file or .bat file during vi job

SOLVED

Hell,

In the import job maintenance area, I am trying to use the "perform path" to run a .pl script or a .bat script after my vi job runs

i am doing a simple test just to get it working..

test.bat is the filename

copy test.txt test2.txt

when i run this .bat file from windows it executes properly

i've tried multiple ways to get this to run but either nothing seems to happen or sage completely hangs up and requires a server restart..

1. put the bat file and txt file in the VI folder on the server, experience number 3 and 4 below
2. put the bat file and txt file in a folder on the workstation,  experience number 3 and 4 below
3. when i put "~" in front of the path and filename the vi job runs but my .bat file doesn't execute (or nothing happens at all and no errors)
4. when i put "*" in front of the path and filename the vi job hangs up in the middle of  importing records and i have to restart the server to get sage running again.

does anyone have a simple example for me to try to be able to execute successfully a .bat or .pl file on completion of a vi job?
(i have scoured sage city and haven't found an example that works in my setup)

i'm running sage 100 2013, version 5.00...

 

Parents Reply
  • 0 in reply to magriggs

    MAS90 is left over from the original program name. This is why the ODBC driver is SOTAMAS90 which stands for State Of The Art Master Accounting Series of the 90s. The MAS90 in the path stands for Master Accounting Series of the 90s.  When MAS90 and MAS200 was changed to Sage 100 MAS90 became Sage 100 Standard, MAS200 became Advanced.

    The issue on the running of the perform logic is that with MAS90 it is run from the work station and in MAS200 it is run from the server. I would suggest making the drive letters in the perform logic relative to the server and not the work station.

Children