With Version 3.2, I was hoping for less access violations, but it's still happening.

[bookman]

With the release of 3.2, I was hoping for less access violations, but alas, it is still happening.

I actually stopped using Version 3.1 for a while because of this.

It is a somewhat difficult thing for us to send the entire database over each time to be diagnosed each time we encounter such a problem because there would be confidential information in the database as well.

I think Kinook must find a solution to this problem as it does makes one feel uneasy that somewhere along the way, we may lose data without even knowing about it.

Is there a debug build for UltraRecall 3.2 ?

What does all these access violations mean anyway ?

Apart from one other program, I have never encountered such Access Violations with other application programs.

Perhaps such problems manifest in other ways, such as the famous BSOD for Windows and I do not have many of those each year.

The only thing I can say is that so far, I have not lost any data (as far as I can tell) due to an access violations.