[RESOLVED] [2005] Access objects in 3rd party Tab Control tags

Okay, before I really confuse anyone I have switched to Visual Web Developer 2005 EE.

I am using a free Tab Control from asplib.net and have the tabs within <ConentTemplate> tags, part of the control. I also have the option to insert them as separate pages which I have done for a different tabbed page and it works fine. I don't want to do it for this page though because it would involve creating a seperate page for each tab, and I have a save button outside of the tabs that works for all tabs regardless of whether the page being saved is new or is being updated. Having it on the page and having the contents it's saving on separate pages would involve making a new method on each tabs page and calling them, but any time I have tried calling methods on different pages I have ended up having to give up and find another way.

The problem is that the back end code does not recognize any objects referenced that are within the tab tags. I believe there is a way to to have them recognized by adding a line at the top of the class (an inherits statement perhaps?) but I am not sure. Does anyone have any suggestions/ideas?

I got a response from asplib.net support and they said "Use control's client side event. Or you need use other clent side way".

Would this work? How would I do it?

Anyone?

I read an article that said to try changing the default focus for nested controls but it was meant for a single control. I tried it anyway, adding "DefaultFocus="Tabs$General" but it didn't work. Tabs is the ID of the TabControl and General is the ID of the first Tab. I also tried variations (putting form ID first, trying one specific control instead of all within General tab, etc.) Can anyone tell me what I'm doing wrong or why this won't work?

Show your markup (ASPX), all of it so that we can see the third party control and the page directive at the top of the page. Don't forget to use [code] tags.

I've attached the whole file, it was too long to post.

I have considered using findcontrol at the beginning of the class, but it would mean about 25 findcontrols. Bad enough for this page but another page that will have the same setup has 60+ controls to find.

I tried putting "Dim lblID As Label = FindControl("lblID")" for all necessary controls before page_load. I couldn't put e.item.findcontrol in page_load because the 'item' part doesn't exist. I stop getting errors about the objects not existing put now I get "object reference not set to an instance of an object" at runtime.

Mendhak, are you making any progress?

UPDATE: I had to put a withevents clause for all buttons because i was getting an error, and that replaced the need to use FindControl for the buttons and avoids compile-time errors, but i don't know about runtime errors yet. i tried using a withevents clause instead of FindControl for lblID (the first control accessed at page_load) but it didn't work any better.

MSDN gives this code to declare a DataGridCommandEventArgs:

Code:

---

Dim instance As DataGridCommandEventArgs
            Dim value As Object
            value = instance.CommandSource

---

But I get "object reference not set to an instance of an object" for the last line, is it possible to correct this so that I can use value.item.FindControl in the page_load method?

On second thought I just realized declaring a DataGridCommandEventArgs isn't possible. My bad.

This control does not seem to be properly documented. I tried going through their documentation

http://docs.asplib.net/asplib/TabControl.html

But it's all talking about client side code. I am not sure how it can be accessed in the codebehind especially since it's not a regular ASP.NET control. It seems to be AJAX.

My initial guess would be to go through Tabs.Controls, or Tabs.FindControl, or perhaps the TabPanels have been enumerated which would be in Tabs.TabPanels or Tabs.Panels, which in turn would have a control collection or findcontrol method.

Thanks for the help but I ended up splitting up the page. I now need to figure out how to call the save method from another page, but I posted that as a separate thread.

--Rikki