I get this message when I want to save "opmerkingen" or "toevoeging" from dive 751. Dive 750 en 752 don't have this problem. I can save "plaatje". What can be the problem?
I found another one. The first dive of 2008.
concurrency violation Diving log 5.0
concurrency violation Diving log 5.0
- Attachments
-
- screenshot of violation
- violation.JPG (76.63 KiB) Viewed 21537 times
Re: concurrency violation Diving log 5.0
Hi
Try to use the "Compress Logbook" function in the menu File > Maintenance. This will repair the logbook if there is something unusual. If this doesn't help, please email me your logbook file.
Kind regards,
Sven
Try to use the "Compress Logbook" function in the menu File > Maintenance. This will repair the logbook if there is something unusual. If this doesn't help, please email me your logbook file.
Kind regards,
Sven
-
- Posts: 25
- Joined: Tue Apr 08, 2008 10:49
- Location: Sydney, Australia
Re: concurrency violation Diving log 5.0
I had the same problem and was unable to find the reason. I opened the log book with version 4 and the error went away.
Re: concurrency violation Diving log 5.0
If one of you still have a reproducable dive in the logbook, please email me the logbook file, the dive number and the steps to reproduce the problem. I remember I had this error message in the past and the reason was a wrong formatted dive date (not visible) imported from SmartTrak. But this message could have several reasons, but mostly related to a problem with the dive data.
-
- Posts: 3
- Joined: Mon Jul 12, 2010 21:45
- Location: New Zealand
Re: concurrency violation Diving log 5.0
I'm having an identical problem. I have tried compressing the Log Book but that does not solve the problem.