If there is a requirement to link multiple Ostendo databases to one MYOB file, there are some limitations, therefore whilst technically possible you should always setup a prototype test environment first and test thoroughly before proceeding.

MYOB Classic:

 This can be achieved, however you must first re-set the following generators in one database to ensure there are not conflicts:

• Create a Std Script and copy in the following (Amend the RESTART Values with your own that will never conflict with the other Ostendo database

begin
// Amend Journal Number Generator
executeSQL('ALTER SEQUENCE JOURNALNO RESTART WITH 200000');

// Amend Financial Batch Number Generator
executeSQL('ALTER SEQUENCE BATCHFILENO RESTART WITH 500000');

// Amend Job Order Number Generator
executeSQL('ALTER SEQUENCE JOBORDERNO RESTART WITH 400000');

// Amend Purchase Invoice Batch Generator
executeSQL('ALTER SEQUENCE PURCHASEINVOICENO RESTART WITH 50000');

// Amend Purchase Receipt Number Generator
executeSQL('ALTER SEQUENCE PURCHASERECEIPTNO RESTART WITH 60000');

SHOWMESSAGE('Generators re-set');
end.

MYOB A/R Live:

NB: Both Ostendo databases must be integrating with MYOB with an "AR Style" of Post Invoices and Payments as Journals

• Create a Std Script and copy in the following (Amend the RESTART Values with your own that will never conflict with the other Ostendo database (Use the script shown above)

Do not attempt to post transactions from multiple Ostendo databases when using MYOB sub ledgers (Standard Invoice and Payment Posting) as there will be problems when payments and deletions are read back from the MYOB file.

Xero:

• Create a Std Script and copy in the following (Amend the RESTART Values with your own that will never conflict with the other Ostendo database (Use the script shown above)

QBO:

NB: This should not be considered. as there will be problems