Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 207
  • Last Modified:

Destroying an automation enabled class from within

I have a CMdTarget derived automation enabled class (call it DocClass).

I want to provide a method (say "Close")to this automation class which
destroys itself.

How to do it?

"delete this" leads to assertion failure.

-----------
PS : My VB controller code reads like this:

sub Test()
Dim docs As DocCollection
Dim doc As DocClass
set DocCollection = Application.DocCollection
set doc = DocCollection.Item(1)

doc.Close   '' I want this line to destroy "doc" object and
            '' make it invalid object reference
            '' HOW TO IMPLEMENT THIS???

End sub
0
dvenkat
Asked:
dvenkat
  • 2
  • 2
1 Solution
 
Andy_KeysCommented:
Should you not just release its refercence by doing a set Doc = nothing??
0
 
NorbertCommented:
This is not a MFC Problem Set Doc = nothing from VB does the work.
If the CMdTarget derived class has to do something special if the last reference to the class is released implement this  handling in the OnFinalRelease Function of your class.

I won't steal any points so if Set Doc=nothing is enough for you
please reject my answer an ask Andy Keys for answering the question
0
 
dvenkatAuthor Commented:
Norbert,

Thanks for your answer.

My problem is more fundamental and is related to MFC code (not VB controller code). Actually I am integrating VB scripting engine to my application ('s object hierarchy).

This means, at run time when I create my scripting dialog, I instantiate VB scripting engine, create a COM object, and attach it to the VB scripting engine's name space (say with the name "Application", so that I can make reference to this object in my VB script and go from there.

However when I want to exit the scripting engine, scripting engine is NOT decrementing the reference count of this object (added to its name space). I do not know why (as such there is no need for you to explicitely delete automation objects (ActiveX engine does it for when the reference count =0).

Since the reference count is not getting decremented, even after my application exits, I have a ghost lingering! (You have to go to "running processess view" to kill it). By now you would have figured out my real problem: since the reference count is != 0, when I "close" the application, the ActiveX engine is really NOT closing the project! It just goes invisible.

I thought, doing "delete this" at destructor may help. But it is not helping. Perhaps I have design problem.

Anyway thanks for your effort and answer.
0
 
NorbertCommented:
Because the destuctor is not called when the Object is not released delete this can not help.
You Asked in your question for
doc.Close   
did you try doc.Release() ?
0
 
dvenkatAuthor Commented:
In the MFC code, calling explicitely "OnFinalRelaease" before calling "delete" of this object created with "new" solves the problem.

Thanks

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now