>>>>>>In a foxpro 2.5 program, for some unknown reason a user keeps getting "Unable to process error."
>>>>>
>>>>>I seem to recall I got this and it was some sort of memory issue.
>>>>>it's been a while since 2.5 days...
>>>>
>>>>Is this just happening with one user? What is the OS? I ask, because this was one of the messages that used to come up when the famous "File Handles" issue was active.
>>>
>>>NT 4.0 running this app in cmd.exe window
>>>It does not happen to the user all the time but when it does, I HEAR ABOUT IT.
>>
>>I can't remember the exact Knowlege Base article, but Fox2.x and NT have problems concerning NT holding DOS based dbf's open even after Fox has been shut down. MS has at least 2 articles on it. You may want to check open resources on NT when this occurs. It even would hold Apps open sometimes.
>
>What happens when this error occurs is that foxpro 2.5 closes all files and does not produce an error you can look at. THUS, the help file says only this:
>
>"Unable to process error.
>No error number is returned. Visual FoxPro closes all open files and exits.
>Record your recent actions while using Visual FoxPro and then call Microsoft Support."

Have you checked the NT open resources to see if something you think is closed (and should be closed) is still open? That is when I have seen such errors occur. Sometimes the error in NT will correct itself after a few minutes or even hours, Sometimes it takes days. You need to manually close the open resource at the admistrator dialog. Look up the KB articles on MS's website. They should give you some direction. It has been a year since I've worked with Fox.2X in an NT environment, but there are definetly known and documented problems.