Hi Sharan,

When the TargetUrl is used, then the only UltraWebTab does is creates <iframe> and sets its src to target. That is all.

So, application should do exactly the same if it had line similar to <iframe src="MyPage.aspx"> in its main aspx (or content page).

To "access" on server child control located in TargetUrl, application may use shared objects like Session. For example, if TargetUrl for Tab1 has TextBox1, then application may process OnLoad (or similar) event of that target page and

Session["TextBox1_Tab1_Text"] = this.TextBox1.Text;
Session["TextBox1_Tab1_ID"] = this.TextBox1.ClientID;

To get those values in main page, application may

string text1_text_tab1 = Session["TextBox1_Tab1_Text"] as string;
string text1_tab1_id = Session["TextBox1_Tab1_ID"] as string;

To "access" on client child control located in TargetUrl, application may use following members of tab: elemIframe, findControl(id), getTargetUrlDocument(). Example:

var webtab = igtab_getTabById(clientIdOfUltraWebTab);
var tab1 = webtab.Tabs[0];
var iframe = tab1.elemIframe;
var textBox1 = tab1.findControl('TextBox1');