Form1.closing in VB2005???

[cj]

In VB2003I have been using an exit menu item that issues me.close() then
Private Sub Form1_Closing took care of closing everything down. I don't
see a closing event for form1 in VB2005. What takes it's place?

[Izzy]

Form1.FormClosing()

cj wrote:

In VB2003I have been using an exit menu item that issues me.close() then
Private Sub Form1_Closing took care of closing everything down. I don't
see a closing event for form1 in VB2005. What takes it's place?

[TP]

FormClosing

cj wrote:

In VB2003I have been using an exit menu item that issues me.close()
then Private Sub Form1_Closing took care of closing everything down.
I don't see a closing event for form1 in VB2005. What takes it's
place?

[RobinS]

It's called FormClosing now. (Irritating, isn't it?)

There's also an event called FormClosed that will trigger *after*
the form is closed.

Robin S.
--------------------------------------------------
"cj" <[e-mail] in message
news:ev**************@TK2MSFTNGP02.phx.gbl...

In VB2003I have been using an exit menu item that issues me.close()
then Private Sub Form1_Closing took care of closing everything down.
I don't see a closing event for form1 in VB2005. What takes it's
place?

[cj]

Thanks, TP and Izzy! That was easy.

Izzy wrote:

Form1.FormClosing()

cj wrote:

>In VB2003I have been using an exit menu item that issues me.close() then
Private Sub Form1_Closing took care of closing everything down. I don't
see a closing event for form1 in VB2005. What takes it's place?

[cj]

Irritating, yes. I hope they had a good reason for it but ...

Yea, I knew "closed" existed but haven't had a use for it yet.
RobinS wrote:

It's called FormClosing now. (Irritating, isn't it?)

There's also an event called FormClosed that will trigger *after*
the form is closed.

Robin S.
--------------------------------------------------
"cj" <[e-mail] in message
news:ev**************@TK2MSFTNGP02.phx.gbl...

>In VB2003I have been using an exit menu item that issues me.close()
then Private Sub Form1_Closing took care of closing everything down.
I don't see a closing event for form1 in VB2005. What takes it's
place?

[Chris Dunaway]

cj wrote:

Irritating, yes. I hope they had a good reason for it but ...

FormClosing has an argument that tells *why* the form closed.

[RobinS]

That's a good thing. But they didn't have to change the
name from Closing to FormClosing. (Although actually,
I guess they changed it from Unload to FormClosing). They
didn't change the Load event to FormLoading. Where's the
consistency? Oh, the drama of it all! ;-)

Robin S.
----------------
"Chris Dunaway" <du******@gmail.comwrote in message
news:11**********************@j72g2000cwa.googlegr oups.com...

cj wrote:

>Irritating, yes. I hope they had a good reason for it but ...

FormClosing has an argument that tells *why* the form closed.

[Chris Dunaway]

RobinS wrote:

That's a good thing. But they didn't have to change the
name from Closing to FormClosing. (Although actually,

Since the Closing event is still present (though deprecated), perhaps
they changed the name to avoid causing any further backwards
compatibility problems.

[RobinS]

Ah, I see. Fair enough. Well, they could call it "George"
and I'd still use it. I'm just *that* flexible. ;-)

Robin S.
----------------------------
"Chris Dunaway" <du******@gmail.comwrote in message
news:11*********************@73g2000cwn.googlegrou ps.com...

RobinS wrote:

>That's a good thing. But they didn't have to change the
name from Closing to FormClosing. (Although actually,

Since the Closing event is still present (though deprecated), perhaps
they changed the name to avoid causing any further backwards
compatibility problems.