Hi Edward,

If a retrieval function supports reading a different database location, such as retrieving a subledger batch into Adagio Ledger, then there will be a path at the top of the retrieval screen that where you can specify the data location.

We prefer not to support the model of copying data files around in Adagio, as there is no guarantee that the new company has all the necessary rads to recognize the contents of the copied data file, but instead have the program do the validation of existing vendors, customers, accounts, etc. We think that being able to edit Archived Batches just like Open Batches, with reporting capabilities and control files outweighs what you might gain from keeping batch files in individual files for copying. This is why Ledger and Receivables and Invoices have Export Batch functions, where moving batches would be done by exporting from company A and then importing into company B. Admittedly, Payables does not have Export Batches functionality, and this would be a good suggestion for the future.

For batch information that is created with a Retrieval file rather than Directly, it is possible to copy that retrieval file to a place that another company can read it, as long as you know what you are doing.

With Payables or other batch-oriented programs that don't have Export Batches, it may have been possible to create a GridView view to export the invoice batch with a format that could be imported into a different company, but the effort to create that view might possibly be more than re-keying the batch. It all depends.