Paco Hsiao
asked on
Free an OCX module from memory
When my VB program is not closed normally, there are some OCX module are still remaining in memory which are not free from memory. So there is any tools or method to free OCX module like using WPS to free VBX module on VB3.0 environment? (This OCX module can not be seen when my program is executed, that is the OCX module there is no user interface for user like Timer object).
Concurs with volking. Your problem is not *how* to release ocx's but *why* they are still there after the app has terminated. I would suggest lots of setting forms to nothing and object variables to nothing as a solution. I cant see a situation where a vb app will always terminate normally except with calls to api functions which cant be trapped.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
OCXs often interrelate to other OCXs, DLLs, etc.
Forcing an OCX to terminate can cause severe problems including registry corruption, file system corruption, memory corruption, and lots of other bad things.
I'd STRONGLY urge you to pursue the question, "Why Didn't The OCX terminate Properly?"
Meaning. "Fix the problem! . . . Don't kludge a patch that has the potential to REALLY SCREW UP THINGS!"