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...

 

  • 0

    MAS90 or MAS200 or the SQL version?

  • 0 in reply to BigLouie

    MAS90 but it's listed as sage 100 advanced erp 2013.. i'm new to the world of sage

    i'll be sure to mention that in future posts.

    thanks

  • 0 in reply to magriggs

    That is not MAS90, MAS90 is Sage 100 Standard.  Advanced is MAS200.

  • 0 in reply to BigLouie

    If Advanced is MAS200 then why does the path on the server say "MAS90"?

    Sage is playing mindgames with me...

    here's my path to the home directory on the server

    \\LACASITA\Sage 100 Advanced ERP\MAS90\Home

    here's what i see when i click Help->About...

    Sage 100 Advanced ERP 2013

    Nevertheless, is there a chance that I can run a .pl or .bat file from the perform path oncompetion of a vi job?  Biglouie, i'll pay you to help me with this and other questions.

    thanks

  • 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.

  • 0 in reply to BigLouie

    MAS90 was originally the file server version. When the client server version came out it was MAS90 C/S for a couple of years before it was changed to MAS200.  But everyone still called it MAS90 no matter what version they were on.

  • 0 in reply to magriggs
    verified answer

    ok, yes, so it seems that the MAS90 on the server is simple old nomenclature.

    as Sage is running on the server then yes I do in fact have MAS200.

    I removed the "~" or the "*" and entered the path on the server to my .pl or my .bat file and sage appeared to run the script.  The script was unsuccessful with errors but it appeared to actually run the script which closes this question.

    Answer - I removed the "~" or the "*" and sage ran the script that i put in the command line with the full path.