Thanks, Marc. We just found today that another program (Outlook e-mail) was causing a 100% usage on the processor - NOT the network itself. Strange, but testing has now begun to isolate the actual problem. Right now the thought is the processor is bad. And our SEEKs are behaving since Outlook was moved elsewhere temporarily.

Barbara

>.... and you are sure that nowhere in the system, the seek procedure has been overwritten? Just a thought. Trying to be helpful and keep the faith ...:)
>
>Marc
>
>
>>I have a SEEK() function that occasionally (about 1 time in 100) fails to return ANYTHING.
>>

>>lRet = seek(cSeek, 'MyTable', 'MyTag')
>>
>>If lRet
>>   End Transaction
>>else
>>   Rollback
>>endif
>>

>>I get a type mismatch error, and Debug shows that lRet is .NULL.
>>
>>I can't duplicate it on demand, but it sure messes up the program.
>>
>>Any ideas?
>>
>>TIA
>>Barbara