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!

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
http://I.Am/DougSteele
(no e-mails, please!)

"accesswanabe" <accesswanabe@discussions.microsoft.com> wrote in message 
news:BE3885C7-769C-4425-9CCB-9735A1718391@microsoft.com...
>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! 

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?

"Douglas J. Steele" wrote:

> 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
> http://I.Am/DougSteele
> (no e-mails, please!)
> 
> "accesswanabe" <accesswanabe@discussions.microsoft.com> wrote in message 
> news:BE3885C7-769C-4425-9CCB-9735A1718391@microsoft.com...
> >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! 
> 
> 
> .
> 

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
http://I.Am/DougSteele
(no e-mails, please!)

"accesswanabe" <accesswanabe@discussions.microsoft.com> wrote in message 
news:9DB85346-9EB3-46B7-A511-15257A9B93E3@microsoft.com...
> 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?
>
> "Douglas J. Steele" wrote:
>
>> 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
>> http://I.Am/DougSteele
>> (no e-mails, please!)
>>
>> "accesswanabe" <accesswanabe@discussions.microsoft.com> wrote in message
>> news:BE3885C7-769C-4425-9CCB-9735A1718391@microsoft.com...
>> >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!
>>
>>
>> .
>> 

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

"Douglas J. Steele" wrote:

> 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
> http://I.Am/DougSteele
> (no e-mails, please!)
> 
> "accesswanabe" <accesswanabe@discussions.microsoft.com> wrote in message 
> news:9DB85346-9EB3-46B7-A511-15257A9B93E3@microsoft.com...
> > 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?
> >
> > "Douglas J. Steele" wrote:
> >
> >> 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
> >> http://I.Am/DougSteele
> >> (no e-mails, please!)
> >>
> >> "accesswanabe" <accesswanabe@discussions.microsoft.com> wrote in message
> >> news:BE3885C7-769C-4425-9CCB-9735A1718391@microsoft.com...
> >> >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!
> >>
> >>
> >> .
> >> 
> 
> 
> .
>