>>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,