bug... well sort of... nah, not really... but a gotcha...

[John Esak]

Hi,

I'm cc'ing this to support as well as here. It is more of a warning than a
bug report. Since you probably never do this, it isn't a bug, but
nonetheless it can byte you.  I only noticed it because it was the very last
thing I had done before things were working perfectly.

I got a SEGV (on SCO O/S 5.7) when running filePro 5.6.6. Don't know if this
affects Windows... it doesn't seem to, but didn't do a thorough test.

What happened was I edited my edits file by hand because it was missing the
TM24x12 edit which I needed. I'm working on an older system that didn't have
it.  So I cut and pasted it into the edits file with "vi".  BANG!  Every
time I went into *clerk from then on I got a SEGV.  Turns out I had
inadvertently added a blank line at the end of the file beyond the newly
added edit.  BANG!

So, as the doctor said "Don't do that..."

Actually, had this not been the very last thing I did before the trouble...
and maybe done 20 other things and then left for the night... sleeping
through the weekend and then starting up again, after first adding in two
new updates and adding 200 lines to the current processing table... this
would have been a bear to find. :-)  Hence, my warning. :-)

John Esak
John.esak at 21appr.com
(717) 985-0200 xt 1141

Visit The FP Room
www.tinyurl.com/24op6x