This post only applies to the Legacy database! We now have a web-based database that is a great solution for those needing access for multiple people and/or from multiple locations. Visit our website for more information: http://approvedworkman.com/cloud-database.Question: When using Check-out/Check-in, how are conflicts resolved in the shared household-specific data?
Answer:
Background: When a member belongs to a club that is checked out, his/her member record is LOCKED in the Primary DB and UNLOCKED in the Secondary DB. The household-specific data is shared by all members of the household and may be edited by any user working with an unlocked member record. This could lead to a situation where multiple persons in a household are checked out to different users. So, here is what happens if more than one user makes a change to the household-specific data:
* Changes to household-specific data (like address) are generally made based on evaluation of the record timestamps from the secondary database in comparison to the primary database or other secondary database/s. (Most recent change 'wins'.) See the Geneal Guidelines for contact information below for details on phones and email addresses.
* When there is no matching household in the Primary DB, then a new household is created using the data from the Secondary DB. [Matches are based on the Household_ID from the Primary DB (if it exists), otherwise it is based on the Address Line and Zip Code (if not blank).]
* General Guidelines for contact information:
- Phones and Email addresses ADDED in the Secondary DB will be added to the Primary
- Phones and Email addresses EDITED in the Secondary DB will be ADDED in the Primary (which may result in extra records that need to be removed manually).
- Phones and Email addresses DELETED in the Secondary DB WILL BE DELETED in the Primary.
*All updates are noted in the log and should be reviewed for accuracy and any items that need attention!!
