On Current Event seems to be disabled for .requery

[accesswanabe]

I am adding some featuring to a form that someone else designed (they are no
longer available for questions about the form). I normally expect the On
Current Event to launch whenever a .requery operation is requested in any
other procedure in the same form. However, with this form, a .requery does
NOT launch the On Current Event. Anyone have an idea what setting might be
responsible for producing this particular behavior? Thanks much!

 

[Douglas J. Steele]

Does it fire otherwise?

Sometimes procedures get disassociated from the events to which they're
supposed to be associated. Look at the Properties sheet for the form. Does
it still have [Event Procedure] as the value for the On Current property?
When you click on the ellipsis (...) to the right of that, are you taken
into the correct code?

 

[accesswanabe]

Thanks Douglas...I should have noted in my original message that I had
checked to make sure that all of the procedures are associated properly.

Do you have any other thoughts?

Does it fire otherwise?

Sometimes procedures get disassociated from the events to which they're
supposed to be associated. Look at the Properties sheet for the form. Does
it still have [Event Procedure] as the value for the On Current property?
When you click on the ellipsis (...) to the right of that, are you taken
into the correct code?

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

I am adding some featuring to a form that someone else designed (they are
no
longer available for questions about the form). I normally expect the On
Current Event to launch whenever a .requery operation is requested in any
other procedure in the same form. However, with this form, a .requery
does
NOT launch the On Current Event. Anyone have an idea what setting might
be
responsible for producing this particular behavior? Thanks much!

.

 

[Douglas J. Steele]

Nothing occurs to me, but you could simply call the Current event in your
code after you invoke the Requery.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

Thanks Douglas...I should have noted in my original message that I had
checked to make sure that all of the procedures are associated properly.

Do you have any other thoughts?

Does it fire otherwise?

Sometimes procedures get disassociated from the events to which they're
supposed to be associated. Look at the Properties sheet for the form.
Does
it still have [Event Procedure] as the value for the On Current property?
When you click on the ellipsis (...) to the right of that, are you taken
into the correct code?

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

I am adding some featuring to a form that someone else designed (they
are
no
longer available for questions about the form). I normally expect the
On
Current Event to launch whenever a .requery operation is requested in
any
other procedure in the same form. However, with this form, a .requery
does
NOT launch the On Current Event. Anyone have an idea what setting
might
be
responsible for producing this particular behavior? Thanks much!

.

 

[accesswanabe]

Yep, that's my work around...just seems really wrong somehow to do it that
way. Thanks much for your help!

Nothing occurs to me, but you could simply call the Current event in your
code after you invoke the Requery.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

Thanks Douglas...I should have noted in my original message that I had
checked to make sure that all of the procedures are associated properly.

Do you have any other thoughts?

Does it fire otherwise?

Sometimes procedures get disassociated from the events to which they're
supposed to be associated. Look at the Properties sheet for the form.
Does
it still have [Event Procedure] as the value for the On Current property?
When you click on the ellipsis (...) to the right of that, are you taken
into the correct code?

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

I am adding some featuring to a form that someone else designed (they
are
no
longer available for questions about the form). I normally expect the
On
Current Event to launch whenever a .requery operation is requested in
any
other procedure in the same form. However, with this form, a .requery
does
NOT launch the On Current Event. Anyone have an idea what setting
might
be
responsible for producing this particular behavior? Thanks much!


.

.