Why does the tab control "OnClick" Event not fire when a tab is clicked?

Oops, suppose I should read all of the question.

>the user has to actually click on the actual page, not just the tab, for the event to be fired.
Just clicking on the tab fires the TabControl_Change event fires, with the value of Me.TabControl being whatever the PageIndex is of the tab the user clicked.

I haven't experienced in any version of Access where the user has to click on the tab, then the page, for the TabControl_Change event to fire.   If there was a subform on the tab, then when clicking on the tab THAT subform's OnFocus event would fire.

Just out of curiosity, what code are you trying to run in the TabControl_Change event?

Hope this helps.
-Jim

> I know the way it works is if a tab is clicked, the user has to actually click on the actual page, not just the tab, for the event to be fired.<

Not in my apps.  You don't see the page until you click on the appropriate tab. In my forms with a multipage tab select, I make each page the same size.  There is no way to select a different page except by the tabs.

Jim, If the user clicks on a tab, the associated page will open.  If the user then clicks on that page (anywhere EXCEPT within a subform), the TAB'S OnClick event will fire - I have verified this and in Access 2003 it is fact.  What I don't understand is why the user has to click the PAGE for the tab's OnClick event to fire when the event belongs to the tab.  It's backwards...

I have subforms on each page that are populated based on a form global recordset within the main form.  Each subform is in a different page.  When the user clicks on a tab that is associated with each page, I want the recordset's to populate (or refresh) for that specific page's subform.

GrayL...  I'm not sure what you mean by this.  I haven't stated that I don't see the page when I click on the tab?  I said the user has to click on the page for the associated tab's events to be fired.

Thanks for your explanation LPurvis.  I will assign you points for this since it's the best answer I'm probably going to receive :-)  No offense to you, it's probably the best answer available...  I just don't see what would be so hard about allowing the tab's OnClick event from running when a user "clicks" the tab - as would be assumed based on the name of the event and what it does anywhere else within the Access application.  I realize it would be somewhat of a duplicate to the entire tab control's OnChange event, but duplicate events exist everywhere throughout the application.  However, I will stop here.  This was not meant to be posted as a complaint as no one here can do anything about it :-)  I wanted an explanation and you provided that.  Thanks!

The way I do it is to use a tab.visiblechanged
example


Private Sub TabPage1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles TabPage1.VisibleChanged
        If TabPage1.Visible = True Then
            MsgBox("Launch your code here!")
       End If
    End Sub

In VBA / Access ?? :-s

My experience is that I cannot get the OnClick event to do anything. I put a message box within the event to know when it fires. It doesnt fire regardless of where I click. I called my function within the Entered event and it works well.