I purchased Diving Log 5.0.2 a couple of months ago and installed and was running it fine on Win7 x64. It has been several weeks since I last used it and tried using it over the weekend when I encountered the following problems:
- Diving Log launches fine, but my default logbook is not loaded by default.
- I open my logbook mdb from the File menu and Win7 pops up an error dialog that Diving Log 5.0 "has encountered a user-defined breakpoint" and has stopped working. Win7 then tries its usual "attempting to find solution for the problem" routine and shuts Diving Log down.
- If I create a new logbook mdb from the File menu, the empty database is created on disk and then the same error immediately occurs when Diving Log attempts to open the new logbook.
- I have deinstalled and reinstalled Diving Log, same problem, no resolution.
- I have opened the mdb's in MS Access and they seem fine as far as I can tell.
- I have an old WinXP machine on which I temporarily installed Diving Log. On this machine I was able to successfully load my original logbook and the empty test logbooks. So, I think this shows that the databases are okay and some type of corruption is not causing the problem.
DaveZ