>>Hi Rob,
>>
>>My first thought was a corrupted table and/or index as well. However, corrupted tables and/or indexes don't become uncorrupted just by rebooting the OS which is what eliminated the problem here. The app has been installed for approx 9 months and this was the first time this happened and it hasn't happened since. Fragmentation was 0% and Scandisk revealed no bad sectors or file segments. For now, I'm chalking this one up to a cosmic PITA and will dig deeper if it ever happens again.
>>
>>>>>I'm going to run a scandisk and defrag on his machine and see what that turns up. Do you know of any utilities that can check for things like faulty RAM?
>>>>
>>>>Unfortunately don't know a "reliable" one. I was having intermittent hangups few months ago. I changed every hardware piece one by one and faulty one was floppy drive (reinstalled others) ! Can you believe a floppy would cause it.
>>>>Cetin
>>>
>>>PMFJI: When I have seen this problem, its really that the error message is misleading --> it means "alias not found" - IOW: the table didn't get opened for which the alias is needed, and it thinks the alias is just a memvar. So, as stated before, I suggest looking at corrupted table and/or index that prevents the table from being opened and then the code that refers to it uses the alias -- which is no longer valid since the alias and current table don't match...
>>>
>>>HTH
>>>
>>>Rob
>
>Hi Colin:
>
>Well, it was worth a try. Good luck & I hope it doesn't happen again...
>
>Rob

Thanx. Me to.