Re: Interaction with office programs
From: R. Hendriks (R.Hendriks_1_at_uvt.nl)
Date: 12/27/03
- Previous message: Peter E.C. Dashwood: "Re: CoBOL moved to OO"
- In reply to: Thane Hubbell: "Re: Interaction with office programs"
- Next in thread: Peter E.C. Dashwood: "Re: Interaction with office programs"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 27 Dec 2003 20:42:44 +0100
> One additional follow up tip. Use the Release method against any
> selection object you obtain when you are finished. In fact, use the
> Release method for each interface (object reference) obtained when you
> are finished. I found through experience that under Windows 9x this
> limitation can be reached without being in a tight loop but instead
> just by not releasing references no longer used. I do not *KNOW* that
> Fujitsu calls the Release method if the reference is set to Null.
> Since Fujitsu COBOL does know that the object is an OLE object - it
> might.
And it seems to do just that! At least page 854 of the NetCOBOL users guide
states:
'The special classes *COM, *COM-ARRAY, *COM-EXCEPTION used in COM client
function internally hold the COM server, COM array, and COM exception
information.
They are simultaneously released when objects holding them are released. Be
sure
to release these objects to be used in COM client function, when they have
been
used. An object is released by setting another object reference (NULL object
is used
only for releasing) in the object reference data item.'
I'll keep your experiences with COM in mind, thanks!
- Previous message: Peter E.C. Dashwood: "Re: CoBOL moved to OO"
- In reply to: Thane Hubbell: "Re: Interaction with office programs"
- Next in thread: Peter E.C. Dashwood: "Re: Interaction with office programs"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
