User Control Question: Button Onclick Event won't work (won't fire)

[Chad]

I have a link (.ascx) and that generates an Add form on that page. The
autopostback dropdown is within a "If Not IsPostBack Then" statement.
The form that is created is all via static html in the user control.
The problem is, no matter what even when no data is filled out in the
form, the submit button just postsback the page and nothing happens. I
have 2 dummy links on the page right now, and the form is automatically
created without a link click for testing purposes. I thought that
onclick events work in a user control but maybe I'm wrong.

Oh, and stuff works in the .ascx, for instance response.write' s appear
from the Page_Load, it's just this onclick event that won't work.

Here's the code:
Sub Page_Load(Sende r As Object, E As EventArgs)
'Constants, link, local path, and sql connection.
strLink =
System.Configur ation.Configura tionSettings.Ap pSettings("Link Path")
strPath =
System.Configur ation.Configura tionSettings.Ap pSettings("Site Path")
Conn = New
SqlConnection(S ystem.Configura tion.Configurat ionSettings.App Settings("SQLCo nnect"))
strBaseQuery = "Select TableName from TableGenData where Display = 4
Order By TableName Asc;"

If Not IsPostBack Then
conn.open()
'Populates the dropdown with the Status Names.
cmdSelect = New SqlCommand(strB aseQuery, Conn)
dtrTableData = cmdSelect.Execu teReader()
TableDropDown.D ataSource = dtrTableData
TableDropDown.D ataTextField = "TableName"
TableDropDown.D ataValueField = "TableName"
TableDropDown.D ataBind()
dtrTableData.Cl ose
conn.close()

Dim li As ListItem
li = New ListItem("Selec t a Table", "0")
TableDropDown.I tems.Insert(0, li)
End If

'The control is added here.
ctlControl = LoadControl( "AddDB.ascx " )
plhContent.Cont rols.Add( ctlControl )
'<ManageDB:AddD B ID="ctlAddDB" Runat="Server" />
End Sub

*************** ********
Here is the control:

'On button submit, grab the data from each form and submit it to SQL.
Sub SubmitForm_Clic k(s As Object, e as EventArgs)
Response.write( "omg it worked" )
End Sub

Now, of course there is a form below that has all the .text fields but
I'm hoping you can imagine those being there. The .ascx also contains
the <asp:Button OnClick=SubmitF orm_Click runat=server /> as well. If
anything, I tried getting it to just error on me and nothing would
happen. I'm not sure if you would need more info, but if so I have
absolutely no problem providing it.

I looked around groups, and around forums for about an hour but I
couldn't find an answer. Maybe I'm just looking in the wrong places,
with the wrong search terms.

Thanks for the help in advance!

[Chad]

Can anyone at least answer this question?

Can onclick events work in user controls? If so, can someone give me a
basic example?

[jhcorey]

Chad,

Yes, the events will work, but everything has to be in place.
I typically let the IDE sort of generate the button click routine, so
it looks like this:
Private Sub btnOk_Click(ByV al sender As Object, ByVal e As
System.EventArg s) Handles btnOk.Click

and then you shouldn't need the "OnClick" in the html. I've seen it
both ways.

Note that the pageload for the containing page will occur before the
event
for the button click. It helps to understand the sequence of events.

One thing to watch for is if you have multiple controls you should
assign them each an id , otherwise things can get confused when
postbacks occur.

[Chad]

Thank you, I figured the events would work... I guess I'm just missing
something.

That does shed some light on the issue.

I have been doing asp.NET development for a while, but I just started
using user controls, so this concept is all a bit foreign to me and
most resources I look at don't tend to cover events in the user
control, but let the even get handled in the page containing the user
control.

Thanks.

[Chad]

I found the problem, and it was just me being stupid.

I had:
Sub SubmitForm_Clic k(s As Object, e as EventArgs)
If blnIsValid = True Then
Response.write( "omg it worked" )
End If
End Sub

I erased the entry on accident that made the boolean value = true. So,
thanks, and I apologize for making such a ridiculous post. I also can't
believe how long this took me to figure out.