I liked Dive Log Manager and the fact that the iOS SW and the OSX SW were from the same company so much, that I purchased DT. I then downloaded my log from my device to DT. I then made a back-up of this initial DB. I then made some changes on my device. On the next two-way sync, the message box indicated that my buddy records had been deleted, and sure enough, they had! And the some country and city information. I need help to get this resolved.
Why is this happening?
Am I doing a sequence wrong?
How can it be resolved?
Loose my buddies when syncing to DT from Dive Log
Re: Loose my buddies when syncing to DT from Dive Log
We are currently in direct email contact with this user to work out what is going on with their logbook. I will post back the resolution here once we get it sorted out in case anyone else is having the issue.
One general tip that might help others is to remember after using the "Two-way Sync" option, you still need to tap the "Use new Logbook" button on the iOS device to actually load the logbook once it has been transferred from the Mac. Otherwise, you'll still be looking at the old logbook on the iOS side. I don't know if this is a factor in this situation, but the need to tap the "Use new Logbook" button in Dive Log is not obvious (sorry about that) and has tripped up other users.
Cheers,
Greg
More Mobile Software
http://www.moremobilesoftware.com
One general tip that might help others is to remember after using the "Two-way Sync" option, you still need to tap the "Use new Logbook" button on the iOS device to actually load the logbook once it has been transferred from the Mac. Otherwise, you'll still be looking at the old logbook on the iOS side. I don't know if this is a factor in this situation, but the need to tap the "Use new Logbook" button in Dive Log is not obvious (sorry about that) and has tripped up other users.
Cheers,
Greg
More Mobile Software
http://www.moremobilesoftware.com
Re: Loose my buddies when syncing to DT from Dive Log
We've managed to sort out what was causing the issue in this case. It turns out that the initial logbook database was generated by a 3rd party application before it was imported into Dive Log DT. This third party application mistakenly left some fields unset (record time stamps and unique identifiers) that are necessary for two-way sync to determine which records should be used in the final logbook. All Dive Log/Dive Log Manager/Dive Log DT database should always have these fields set but in the case of this particular logbook they were not resulting in the records being interpreted as having been deleted.
This issue is a result of a deficiency in another application and will not affect normal syncing between Dive Log and Dive Log Manager/Dive Log DT. We are working with the 3rd party application developer to correct this deficiency. If anyone else encounters a similar issue, please contact us via our support email address (support 'at' moremobilesoftware 'dot' com) and we can correct your database for you so that you will not experience the issue again (Dive Log Manager/Dive Log DT takes a backup automatically before a two way sync that contains the original data if you see the issue).
Many thanks to "Zesty" for his patience and helping identify the issue and for providing the data we needed to sort out the solution.
Cheers,
Greg
This issue is a result of a deficiency in another application and will not affect normal syncing between Dive Log and Dive Log Manager/Dive Log DT. We are working with the 3rd party application developer to correct this deficiency. If anyone else encounters a similar issue, please contact us via our support email address (support 'at' moremobilesoftware 'dot' com) and we can correct your database for you so that you will not experience the issue again (Dive Log Manager/Dive Log DT takes a backup automatically before a two way sync that contains the original data if you see the issue).
Many thanks to "Zesty" for his patience and helping identify the issue and for providing the data we needed to sort out the solution.
Cheers,
Greg