Dll hanging on.

[Iain17]

Hello all. I have another problem for you.

Here's the deal. I have two COM objects written in VC++. I did not write these. These dll's control all of the access to the database that my VB GUI accesses. All of the tables in the database have been implemented as class objects in the Dll. For each table there is a list object with Count and Item properties, and Add, and Delete methods. There is also an item Object. This holds the info from the database for each record. Anyway that is all probably useless info.

I have referenced these dll's in my project, and use CreateObject to create an instance of the dll. The user then bangs away at the gui, adding deleting amending etc. Then when they are finished they close the App.

Now when the application closes down i set all object references to nothing, and generally clean up. This works bloody marvellously under NT. However, Windows 95 and 98 is a different story.

When the application closes down in 9x, it all appears to shut down correctly, but if you look in the task manager, the application is still listed, but it is not responding. We are pretty sure that the problem lies in the dll somewhere, but cant for the life us find it.

I was just wondering if anyone else has had problems like this and has a soloution, or if you can shed some light on what may be happening.

Regards,
Iain.

[Ianpbaker]

Hi Iain

It could well be that the dll is not terminating correctly as you said, but it could be a problem with the actuall dll itself.

Also there is a stupid but common problem causes the app to still be open (Iv'e done it many times myself). When your opening and closing window's within your app do you use the the form.hide to close it? if yes, the form does not get unloaded when you close your main app screen and just sit's there in memory twiddling it's thumb's. To sort this out use the unload command to completly terminate the form.


Hope this helps

Ian

[Iain17]

Ian,

Yeah, i have been tricked by the hidden form businss before, but i can assure you that is not the problem. I still think the problem is in the dll, but seeing as i did not write the dll, i cant check it out.


Anyone else got any ideas on the matter ?