Sage 100

Chain a VI Export to VI Import - can it be done? We often do a VI Export of selected data to be the source file of a VI Import to update related fields for only those selected data items. Currently you have to run the Export, then run the Import. I haven't been able to chain an Import from Has anyone found a way to reduce this to one step? Maybe doing it through a batch file to run both of them?

.Bat file is a good way. Below example has an export followed by an import (VIWX02 followed by VIWI02).: N: cd \ cd mas90 cd home PVXWIN32.EXE ..\launcher\sota.ini ..\soa\STARTUP.M4P -ARG DIRECT UIOFF fed 1234 ABX VIWX02 AUTO PVXWIN32.EXE FEDEXG PVXWIN32.EXE ..\launcher\sota.ini ..\soa\STARTUP.M4P -ARG DIRECT UIOFF fed 1234 ABX VIWI02 AUTO

ditto to Doug.

@DougHiggs what does is the purpose of second to the last line? (PVXWIN32.EXE FEDEXG)

It is irrelevant to the VI jobs. I should have removed it. I copied this from a batch file I set up for one of my clients. FedEx ship manager appends a text file after each order is shipped. The text file has the Sage order number, package #, tracking #, and freight amount. VIWX02 exports the invoice number and sales order number from so_invoiceheader. FEDEXG is a ProvideX program that finds the invoice number using the text file created by FedEx ship manager and the text file created by VIWX02. FEDEXG creates a text file with the invoice#, tracking#, package#, freight amount. VIWI02 imports the text file created by FEDEXG to so_invoicetracking. There is another VO job not shown above that uses the same text file and imports to so_invoiceheader.

Good grief! @DougHiggs Why hasn't someone developed a reasonably priced utility program to handle this? I'll give you credit for solving the problem even though it looks like hand stands and back flips to do it.

LOL... and a couple of cartwheels.