TabStrip index values differ from MouseDown to MouseUp. Am I doing something wrong?

I can't replicate that result. In the MouseDown event, the value of the tabstrip is the value of the current tab. In the MouseUp event the value of the tabstrip is the value of the new tab.

I noticed you using the term index value. The .TabIndex of a Tabstrip, like the TabIndex of any control, it its index in the tab order of its surrounding container (userform, frame or page). It has nothing to do with the selection made by the user.

Hi, mikerickson,

Thanks for your reply. You're quite right, of course: I used an inappropriate term in my post. The index I was referring to was, as you rightly surmised, in fact the tabstrip.Value and had nothing to do with the tabstrip.TabIndex. The tabstrip.Value, however, if I understand things correctly, is passed on to the MouseDown/MouseUP event handlers under the guise of "By Val Index" and this is what I used in my simple boilerplate code "Select Case Index" -- Wait! Let me try something. BINGO! I changed the code to "Select Case tabstripname.Value" and the code now works like I remember it doing in earlier drafts.

This clears up for me why a functioning code suddenly stopped working but my original question still stands, I'm afraid. I don't understand your reply. What "new tab" are you referring to? The "current tab" I take to be the tab clicked which fired the MouseDown event handler and this produced the expected result using "Select Case Index". Why should Case Index always = 0, then in the subsequent MouseUp handler? What has caused the value of By Val Index to be different?

Thanks for your time,

Ken Wilson