Releasing VB6 Application from NT Task Manager

I have a VB6 application that when I unload it, it doesn't remove the application from the Windows NT Task Manager List.  This same application in was previously in vb4 and this never seemed to occur.  If it is run over and over, the number of instances in the Taks manager multiplies.

Any help would be appreciated.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You are probably using the DataReport Designer ?
If so:
After using the .PrintReport method you must UNLOAD the DataReport yourself, otherwise it will stay in the Task Man after closing the application.
Did have the same problem....
grtx, RoverM
facoleAuthor Commented:
Per Proposed Answer from roverm.  I am not using the DataReport Designer in my application.  Something else must be causing it.  Thanks for the try though
Do you have multiple forms in your program?  

Does it only happen when the "X" is used to close the program?

I had a similar problem, you have to be sure and unload all forms before a program will fully close.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

Are you using any DAO objects?

If you set references to DAO objects like databases or recordsets, you have to explicitly set these object references to nothing to get rid of them:

Dim rs as DAO.Recordset
Set rs = somekindofrecordset
'     do your
'     recordset work
'     here
Set recordset = nothing 'this detroys the reference.

If you don't, many times they hang and create the situation you are describing.

Can you give anymore information what you're using in your application?
facoleAuthor Commented:

Thank you.  I found a form that I loaded, but didn't necessarily display all of the time.  It was always loaded and on exit it was never closed.

Thanks for your help
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.