Current event fires twice - how to excute code just once?

[doctorle]

I'm surprised that the Current event of forms always fires twice
(Access XP).
I have quite a lot of processing done in the current event, how to make
the code run just once?

Thanks

[Rick Brandt]

<do******@hotpop.com> wrote in message
news:11**********************@g10g2000cwb.googlegr oups.com...

I'm surprised that the Current event of forms always fires twice
(Access XP).
I have quite a lot of processing done in the current event, how to make
the code run just once?

I have never noticed that happening on any of my forms. Perhaps your actual
code is somehow calling itself or calling another procedure/function that is
producing the second run.

If you have nothing in your current event but a MsgBox() do you see it displayed
twice?

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[Anthony England]

<do******@hotpop.com> wrote in message
news:11**********************@g10g2000cwb.googlegr oups.com...

I'm surprised that the Current event of forms always fires twice
(Access XP).
I have quite a lot of processing done in the current event, how to make
the code run just once?

Thanks

As Rick says, this doesn't sound like any known issue - more likely your
coding. If you created a new blank form based on a table and pasted in:

Dim m_lngCount As Long

Private Sub Form_Current()
m_lngCount = m_lngCount + 1
Me.Caption = CStr(m_lngCount)
End Sub

You would see from the caption that you were going up in ones, not twos, so
the current event must only be firing once.

Is there some form of re-query or re-setting the form's recordsource?

[Bri]

do******@hotpop.com wrote:

I'm surprised that the Current event of forms always fires twice
(Access XP).
I have quite a lot of processing done in the current event, how to make
the code run just once?

Are you are referring to it running twice when a Form (or is it a
subForm) first opens? I've seen this and it seems that there is nothing
you can do to stop it from running twice, but you can put in a test to
see if it is the first time or subsequent times. What seems to happen is
that the Current Event fires when the Form first opens, before the
recordsource is loaded, and then again after it has the recordset and
arrives on the first record. Unfortunately any test for the existence of
the recordsource (or its clone) produces an error if it doesn't yet have
one. You could trap that error so it doesn't get displayed. I don't know
off the top of my head what circumstances actually cause it, but I have
definitely had it happen to me too.

--
Bri