>>>I have a MaxFrame 2.01 app that has 170 operators using
>>>it. It appears that there is a problem with the error
>>>routine in that the errorlog.dbf (a free table) causes
>>>a "record not available" error to scroll across the screen.
>>>The errorlog.dbf contains 10 memo fields. I suspect that
>>>a memo field has been corrupted.
>>>
>>>Anyone else experienced a problem like this?
>>
>>I have - we traced it back to a crawling network. Apparently the .FPT file lock was not getting released after an edit or add.
>
>Dorris, I'm having the same problem with MaxFrame. Could you give more information on the 'crawling network' and the FPT file locks? Just the errorlog memo file? Any FPT file?
>
>Thanks,

Basically, we had a Novell 3.1 server that was incredibly SLOW and on occasion, when the backbone would get particularly busy, the 3.1 network would not release the memo file. I corrected the problem by putting the memo field on it's own page in my pageframe instead of bringing up a "window" for it.

Our hardware people could not come up with any explaination for it. (besides, you KNOW there's NEVER anything wrong with the hardware :) )