Return code 139 (bug?)

Hi all,

Here's an update to the error code 139 incident described earlier.
(like you care!, but hey...)

After digging around more on the return code 139, it again it appears
to be database corruption, with a missing apostrophe in the DB file.

I don't know why two of my databases periodicly get corrupted.  In
high hopes, I just have upgraded from 2.2.0 -> 2.3.0, and am now using
the famous -nolock feature. We'll see what luck I have.

Jeff