IDE vs EXE

Can anybody explain me why the difference between this two logs:

IDE
Board UserControl_Paint
ctlSudoku TB_ButtonClick
Board UserControl_Terminate
ctlSudoku UserControl_Terminate

EXE
Board UserControl_Paint
ctlSudoku TB_ButtonClick
Board UserControl_Paint

The first one is the log for the project being run on the IDE. The second one is the log for the same project being run the EXE. I have to correct this, because if the Terminate events are not fired the objects are not released and the program raises an awful error when it should close itself smoothly. Any ideas how to fix this? TIA,

Instead of _Terminate couldnt you use _QueryUnload?

Quote:

---

Originally Posted by RobDog888

Instead of _Terminate couldnt you use _QueryUnload?

---

There are usercontrols and/or classes. Shouldn't these events fire when the form it contains the usercontrol is unloaded? :confused:

If the form that contains the UC does not unload then the UC will remain in memory and never fire the _Terminate event. Perhaps that may be part of the reason.

Quote:

---

Originally Posted by RobDog888

If the form that contains the UC does not unload then the UC will remain in memory and never fire the _Terminate event. Perhaps that may be part of the reason.

---

But I'm doing "Unload Me", so the UC should be terminated.

I've even change the startup form. It's not longer the form itself but Sub Main.

VB Code:

Sub Main()
    Dim fSudoku As frmSudoku
    
    Set fSudoku = New frmSudoku
    
    fSudoku.Show vbModal
    
    Set fSudoku = Nothing
End Sub

But the terminate events are not fired yet.

Should be, but if you have any referenced objects that are not unloaded or destroyed it can cause the form to atay loaded. Like when doing Office automation from vb6. If you dont close and destroy Office apps/objects it will cause your program or the Office app to remain running.

What do you have that may be causing the form to remain in memory?

The form is not held in memory. Im printing a list of loaded forms before and after unload them... and none gets printed once it's finish this task. However, the UC's control (which is held on another UC) remains in memory.

I've found this article: http://www.developerfusion.co.uk/show/2929/2/ Which I thought it would be the answer for my problem. However, after implementing that solution, I'm still stuck. I have a little doubt with the collection. The items I'm adding to a collection are:

VB Code:

Private iColumn As Integer
Private iLine As Integer
Private iGroup As Integer
Private bValueSet As Boolean
 
Private n_txt As Long    'This was defined as object -> Now, soft referenced
Private n_pct As Long   'This was defined as object -> Now, soft referenced
 
Private iValue As Integer
 
Private sPerColumn As String
Private sPerLine As String
Private sPerGroup As String
Private sMissing As String

Which are member variables which can be accessed through public properties. The question is, should I add a soft reference into the collection or can I just add the object itself?

Found the solution. Got rid of MS Coolbar's OCX. My toolbars are fixed on the top of th usercontrol now :thumb: