Reply to thread

Message

<blockquote data-quote="Inker" data-source="post: 569431" data-attributes="member: 10541">We don't really know what causes the corruption. The only thing we know is that it happens alot more if the db is acessed over the network (wether local or not).My personal oppinion is something interfering with the sole acess to the db3 file (like an AV program briefly interfering). It could also be a bug in the plugin itself, or even a bug in the .net sql lite connector. Or its a weird combination of all of those. For some people it might be a hardware issue. We recently had a few patches by gibman come in that properly close the db before entering standby. It could very well be that this was the issue.I personally never had it happen to me in the years of using the plugin.The other thread wasn't the correct place to discuss db corruption for a local db (that and the poster changed the thread title several times and jumped to a different problem in the middle, then came back obviously without having read/acknoledge what had been said before, hence the closure).</blockquote>

[QUOTE="Inker, post: 569431, member: 10541"] We don't really know what causes the corruption. The only thing we know is that it happens alot more if the db is acessed over the network (wether local or not). My personal oppinion is something interfering with the sole acess to the db3 file (like an AV program briefly interfering). It could also be a bug in the plugin itself, or even a bug in the .net sql lite connector. Or its a weird combination of all of those. For some people it might be a hardware issue. We recently had a few patches by gibman come in that properly close the db before entering standby. It could very well be that this was the issue. I personally never had it happen to me in the years of using the plugin. The other thread wasn't the correct place to discuss db corruption for a local db (that and the poster changed the thread title several times and jumped to a different problem in the middle, then came back obviously without having read/acknoledge what had been said before, hence the closure). [/QUOTE]

Verification