VI - cycles vs. app server (Sage 100 advanced 4.50)
Have three VI jobs that need to run overnight. One exports AP invoices from company code ""A"", next one imports those invoices to AP invoice data entry in company code ""B"", and the last imports ""payments"" into manual check entry in company code ""A"". This is to move AP from one company to parent company. I'd use the cycle feature, but it doesn't seem to allow you to specify the company, just hours, minutes, etc.
In pre 4.40.4 you could create a batch file with VI command line, add it to task scheduler and set it to run. I just got through reading that in 4.40.4 and above for Sage 100 Advanced article 110-405391, you have to create ""Apps"" in the Application Server, then set up the batch file on a workstation and schedule it to run. This contradicts the help file in VI,
""Note Shutting down Sage MAS 90 terminates any job running from a shortcut, whether the job was started before or after Sage MAS 90 was launched.""
Is that why you need to use the Application Server to avoid being logged into Sage 100 run the batch file runs?
So has anyone done it that way - setup the job in the application server, then a batch file on a workstation running from task scheduler? Or can I just run the batch file on the server....