Problem really disposing webbrowse-object

P

pierremans

New Member
Hi,

I use the Internet-explorer ocx in my program (V9.1D09). It works, but I have the problem that the ocx doesn't seem to be 'freed' after closing the window in which it is used.

The problem is that I really need a new 'iexplorer-session' because of a specific cookie i get back from the specific URL I have to use. If the session is not considered to be different, then the cookie will be the same. (I hope that this makes sense :o). Now this only seems to be possible by closing my progress application, which is obviously not the solution I hoped for.

Anyway, I browsed through the documentation and found the quit()-method. But if I try
chCtrlFrame:WebBrowser:QUIT().
Click to expand...
it gives me an error. Now I even read somewhere in the helpfiles from MS that the WebBrowser object even ignores this method! :(

So the question is: does anybody out there:
  1. understands what I am talking about, but mostly
  2. have a solution for my problem
Probably a related issue: When using a DLL in my progress-session, the dll-file seems to be 'in use' even after the release-statement. I have to exit the appbuilder to free the library, which is rather a pain when I want to add functionality in the DLL and test it right away.

Is there anybody who knows a solution for this?

TIA

Pieter
 
I haven't used it but the WebBrowser object apparently has a BUSY method/property that needs to be checked before certain operations can be performed.

Maybe this is related to your issue.
 
On the DLL thing:

If you are talking about DLL procedures (eg. API definitions) as opposed to OCX/COM objects,

Try dropping the PERSISTENT clause on the procedure definition, if there is one (although this may have performance implications).

Try also 'RELEASE EXTERNAL myDLL.'

before exiting the program.
 
Problem solved (Re: Problem really disposing webbrowse-object)

The release external is a OE10-thing if I am correct, so that would not be an option at this point (using V9.1D09).

The releasing-part looks okay but I will check it just to be sure.

But apart from that, it seems that my conclusion was wrong and that my problem was cookie-related! So I bothered you all unnecessary :blush1:

Sorry and thanks for you time
 
You must log in or register to reply here.
Back
Top