Has anyone experienced an issue with a custom module, where it is moved to the Default page (from the page it was added to) when Settings are saved?  This only happens with my custom module.  I tried commenting out the code within the UpdateSettings method of my Settings control, but the control is still moved.

FWIW, the environment that my module is loaded into is running DotNetNuke 6.2.3 on IIS 7.

I've followed your steps and found that the TabID is indeed getting changed in the database.  However, I haven't located any code responsible for changing it.

I've realized that it's also worth noting that my Settings control has a custom usercontrol added to it.  Somehow it's within the custom control that the problem begins.  However, the custom usercontrol has no knowledge of its container (in this case the DotNetNuke Settings control).  What I've learned is that commenting out the line in the code below (in bold font) keeps the module from moving, but the input controls aren't bound and are therefore blank.  I've also placed breakpoints throughout my code and attached to the process, hoping to glean some more useful information.

 Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
    [...]
    If Not Page.IsPostBack Then
        Page.DataBind()
    End If
    [...]
End Sub