While it may be "memory corruption", my bet is that it is of a type caused by the user doing someting that the application didn't anticipate (and so does not 'cover' with code). Resulting in things being in a "state" different than what the program expects.

I'd question the user - better still go sit with him/her - about exactly (repeat: EXACTLY) what they were doing, including describing PRECISELY what the click/hit/select when they say something. Chances are you'll find them doing something in a totally different way than you expect... or doing something else in between steps that messes things up... or doing something else, elsewhere, that is changing something in the base OS structure (such as resetting the 'current directory' or something).

good luck




>My Foxpro applications are typically used by dozens of users. A given operation in a given application may be performed correctly dozens if not hundreds of times per day and work perfectly each time.
>
>Then, a user performs an operation and it producuces strange and unexpected results. That user gets unexpected results for the rest of their session, time after time. All other users doing the same operation at the same time, get correct results. After rebooting, the user getting unexpected results will get normal results.
>
>Conclusion: The user getting strange results has memory corruption.
>
>This problem occurs only in the Foxpro application. All other applications continue to function properly.
>
>This problem cannot be reproduced with any sequence of steps since, everything in the program continues to work perfectly on every other machine. This will happen two or three times a week and on a different machine and user each time.
>
>Does anyone else experience this with their applications? Are there known issues that cause memory corruption with8ing a Foxpro application?