Peer-to-Peer/Direct Upgrade Instructions from v12 and Older to Atrex 16

Taking the time to make sure that every Atrex system is mapped correctly BEFORE installing Atrex 16 will help make sure that the upgrade process goes as smoothly as possible.  While incorrect mapping worked in some scenarios in earlier versions of Atrex, those scenarios will NOT work properly in Atrex 16.

To check your mapping, open Options – System Information on each Atrex system and verify that the Data Path and Central Path on EVERY Atrex system is EXACTLY the same.  If they aren’t, correct as needed under Options – Locations – Reports/Central Location or Options – Locations – Data Location.  Examples:

 

Scenario 1:  (Correct Peer-to-Peer)

  Server:

      Data Path:        \\Server\Atrex\Data

      Central Path:        \\Server\Atrex\Central

  Workstation-1:

      Data Path:        \\Server\Atrex\Data

      Central Path:        \\Server\Atrex\Central

  Workstation-2:

      Data Path:        \\Server\Atrex\Data

      Central Path:        \\Server\Atrex\Central

 

Scenario 1 is the perfect peer-to-peer setup.  All of the stations are pointing to the same physical locations using the same exact paths through the network.

 

Scenario 2:  (Incorrect Peer-to-Peer)

  Server:

      Data Path:        \\Server\Atrex\Data

      Central Path:        \\Server\Atrex\Central

  Workstation-1:

      Data Path:        \\Server\Atrex\Data

      Central Path:        \\Server\Atrex\Data

  Workstation-2:

      Data Path:        \\Server\Atrex\Data

      Central Path:        \\Server\Atrex\Central

 

Scenario 2 will not operate correctly in Atrex 16.  The Central path on Workstation-1 is pointing to the Data folder this will cause errors in Atrex 16.

 

Scenario 3:  (Incorrect Peer-to-Peer)

  Server:

      Data Path:        \\Server\Atrex\Data

      Central Path:        \\Server\Atrex\Central

  Workstation-1:

      Data Path:        \\Server\Atrex\Data

      Central Path:        C:\Atrex\Central

  Workstation-2:

      Data Path:        \\Server\Atrex\Data

      Central Path:        C:\Atrex\Central

 

Scenario 3 will not operate correctly in Atrex 16.  The Central path on the two workstations is pointing to the local hard drives of each system which will cause locking errors when attempting to access the data in Atrex 16.

 

Scenario 4:  (Incorrect Peer-to-Peer)

  Server:

      Data Path:        \\Server\Atrex\Data

      Central Path:        \\Server\Atrex\Central

  Workstation-1:

      Data Path:        \\Server\C\Program Files\Atrex\\Shared\Data

      Central Path:        \\Server\Atrex\Central

  Workstation-2:

      Data Path:        \\Server\Atrex\Data

      Central Path:        \\Server\Atrex\Central

 

Scenario 4 will not operate correctly in Atrex 16.  While the Data paths \\Server\C\Program Files\Atrex\\Shared\Data and \\Server\Atrex\Data physically point to the same folder using different network shares, the Atrex 16 database engine will see these as different paths.  This will result in locking errors when attempting to access the data from Workstation-1.

 

Scenario 5:  (Incorrect Peer-to-Peer)

  Server:

      Data Path:        \\Server\Atrex\Data

      Central Path:        \\Server\Atrex\Central

  Workstation-1:  

      Data Path:        C:\Atrex\Data

      Central Path:        C:\Atrex\Central

  Workstation-2:

      Data Path:        X:\Atrex\Data   (X: is mapped to the 'CDrive' share name on the server)

      Central Path:        X:\Atrex\Central

 

This scenario will not work in Atrex 16 for either workstation.  The Data and Central paths for Workstation-1 are pointing to the local hard drive instead of to the server.  Any transactions created on, or data updates performed on, Workstation-1 will NOT be saved to the live data on the server computer.  This WILL result in inaccurate sales and inventory.  Also, while the Data paths X:\Atrex\Data and \\Server\Atrex\Data and Central paths X:\Atrex\Central and \\Server\Atrex\Central physically point to the same folders using different network shares, the Atrex 16 database engine will see these as different paths.  This will result in locking errors when attempting to access the data from Workstation-2.

 

Upgrading from Atrex 12 and older 

  1. Make 2 separate backups of your data, one to the hard drive and one to some type of removable media.
  2. Confirm your Data and Central paths (per instructions above) and correct as necessary.
  3. Close Atrex on all workstations.
  4. On the first system, install Atrex 16 directly over top of your previous Atrex installation.
  5. Start Atrex 16 and when prompted, start the data conversion.  Allow the data conversion to complete before continuing further.
  6. Install Atrex 16 on the remaining systems.
  7. Enter the Atrex 16 registration key under Options – Enter Registration Information.
  8. Finally, in previous versions of Atrex email setup was entered on each workstation.  This is no longer the case in Atrex 16.  There’s a global email configuration as well as individual user configurations.  If you were previously using MAPI to send email from inside Atrex, or if you weren’t sending email from inside Atrex, no changes are necessary.  If you were using SMTP to send email from inside Atrex your email configuration must be re-entered.  Enter the global configuration under Options – Company Setup / Customization – Company Information and Settings – Email tab.  Optionally, enter individual user configurations under User – Edit User/Group.

Add Feedback