With earlier versions of NOAH System, it has been a simple process to transfer the NOAH Database, the noah.mdb file, to a new PC or new server. If a location added a new computer or needed to restore a backup, a simple copy and paste of the noah.mdb from the old PC to the new would restore all the information from the NOAH System database.
However, NOAH 3.5.2 includes eTONA functionality. eTONA transactions are stored in both the NOAH System database and an additional eTONA database. If a location is using the eTONA functionality and wants to move the NOAH and eTONA databases to a new PC, it is important to keep these two databases together to retain all the information.
The best way to move the eTONA database and the NOAH database to a new PC is to use the Backup andRestore functions. (Refer to Backing up a database and Restoring a database under Related Links to the right of this page.) Once you have created the .bck files, you can transfer them to the new PC and Restorethose files through the NOAH Database Properties Program.
Another important concept with a location using eTONA functionality is the idea of the Database ID. This unique ID is created by eTONA and stored in the NOAH System database. It identifies the eTONA database to the manufacturer that is accepting transactions from the location.
If a location moves the NOAH System and eTONA databases to a new PC AND keeps the original PC active, two computers will have databases that use the same Database ID. This might cause errors at the manufacturer's back office system when receiving status updates.
If the customer wants to continue using NOAH on the old PC, to avoid these errors, replace the relocated databases locally on the machine with a new blank database. Use the Replace function in Database Properties for both the NOAH System and eTONA databases. (Refer to Replacing a database underRelated Links to the right of this page.)