Application not closing properly [RESOLVED]

There's something weird happening on an application I made for a client.

Each time he close the application, it still running in the task manager.

In the IDE, it's closing properly.

I know that when an application is not closing, it means something still running in the application. I used debug.print just because the unload to see what's running.

I'm using the com port, which is closed, a timer, it's disabled and a DB connection which is closed too.

I tried to use the "End" command to completely close the app on the unload. On the IDE, it still working, but on the .exe, I get a Windows error message saying the application encountered errors and had to be closed by Windows.

How can I see why the application is not closing properly ??




Added green "resolved" checkmark - Hack

Are you unloading all your forms? Are you opening a form then hidding it b/c you might not be unloading that one?

Quote:

---

Originally Posted by space_monkey

Are you unloading all your forms? Are you opening a form then hidding it b/c you might not be unloading that one?

---

Even if he is not unloading all the forms etc. the End command should terminate the application.
It seems more of a corrupted system file issue to me.


Pradeep

End is yucky. Don't use it :eek:

VB Code:

Dim f As Form
For Each f In Forms
Unload f
Next f

chem

Forgot to tell you, this is something I test with Debug.Print

VB Code:

Debug.Print Forms.Count

It returns 1, so everything is okay for the forms

What about closing and destorying your objects (like recordset objects, connections objects, etc)? Is that being taken care of?

I always close recordsets and connections.

I'll check if I forgot something, but I don't think that's the problem

In your first post you said this was an application you made for a client.

Is this only happeing on his machine or it happening no matter where you run it?

I didn't try it on other computer.

What I did now, I'm creating a txt file on MDIForm_Unload that show the state of DB connection, COM Port, # of Forms, ...

This way, I'll see where's the problem

Gensor, can you post the code or something? So I can take a look at it? I had a problem like this becuase I was using the form resize but by accident, didnt spell the form name correct and it never closed when running the exe.

Actually, I can't. I know it would be the best way, but first, it's a big application and second, it's in French, so all variables, functions and subs are in French and third, it's a question of privacy. I'm not allowed to show or give source code. My boss would'nt like me if I do that

Gensor,

You know that's like going to the doctor and telling him:

Doc, I have a pain and I don't like it... But I am not going to tell or show you where.

And then expecting him to diagnose and fix the problem properly.

Nice analogy randem. :bigyello:

Quote:

---

Originally Posted by neicedover1982

..... but by accident, didnt spell the form name correct and it never closed when running the exe.

---

Option Explicit will fix that... Always use Option Explicit !

randem

If you did something really stupid and hurt yourself. You'll be too shy to tell it to someone, so, you'll say to the doctor where you're harm, but you'll never tell him how you did to hurt yourself!!

somewhere in your code you have managed to create a circular reference - and this what is keeping your app running.

your job - find that reference.

I don't understand what you mean by circular reference !!

Put a timer on each for for each minute..have it open the app.path & "\info.txt" for instance..

then have it print the timers form and when you close your app, you will see which form(s) are hanging

Gensor,

The doctor would have to see the wound, wouldn't he. You have to show us yours. Post some code or we are just guessing. When it could be obviously clear if we saw some code. Your code can't be so scrective that a excerpt of your code would cause a national security alert.

You might have missed something that was very easy to overlook. Posting some code can't hurt. Extra eyes can always help.

circular reference 1


circular reference 2

I don't mind to post some code, but for this problem, I would have to post all the application. Posting a part of the application won't help you!

Gensor,

So posting none will help HOW?

I thought you would know by experience what are the common problems when an application is not closing properly.

Gensor,

Experience is what make us ask for the code. If everyone coded the same you would not have this problem in the first place. That is why we need to see actual code. Common problems have been given to you. Unfortunately, coders find new ways to create old errors.

Search for 'not closing' and you'll see that the answers are all the same. Usually requires posting the code in question, as we can't read minds.

I'll try to figure it out by myself.

So this is thread is now resolved

Post back when you figure it out.

Okay

Gensor,
Did you by anyway miss my post no. 3.
I'm 99% sure the problem is not with your application, but with the OS/ extenal factors. The END statement terminates the application instantly & unconditionally (though I won't recomment using it). So whether it is a circular reference or resources not released, this problem shouldnot occur.
The surest way to confirm what I said is to try your app on another system. In case the problem is still there, your program is to be blamed, incase the problem goes away your OS is to be blamed.

Pradeep

Actually, I tried it first with a Windows 2000 computer. And now, I have a new computer which have Windows XP on it and I still got a GPF when ending the program with End.

Gensor,

Never use end. It is only there to terminate a specific portion of your app not all of it. It basically there for novices. There are independent portion of you app that you can start active such as API calls, other dll's or objects. You must terminate all processes and objects before terminating your app. End just does not do it!!!!

I know, I usually don't use End.

I only tried it to see if it would close correctly.

If you want to PM me with your email address, I'll reply with mine, and I will look at it, and keep it confidential. If I have any questions, I'll post them here, after PM'ing you with my thoughts.
Let's see if we can solve the problem, and produce a good thread for others!

That's a good idea, but I want to wait first.

I modified my application to create a log file to show me what is still open when the application unloads.

If I don't find what's the problem with the log file, I'll PM you my e-mail.