>Hi,
> Do you meant that is not caused by my application? Instead, it caused by VFP when allocate/deallocate memory?
> If yes... what should I do? Nothing?
>
>Thank you

These types of errors are not things you should normally see. There are things you can do to help get rid of them..

- Make sure that all ActiveX controls and DLLs on the user's system are properly registered and the correct version
- If you CREATEOBJECT() in a routine, make sure you set the variable refence to NULL before it is released.
- Determine if the user has the proper video and printer driver installed and they aren't corrupt.
- SCAN DISK the user's hard drive. I've seen times when this fixes VFP problems
- The problem could by an interaction with another running application. Sometimes the load order can make a difference