|
More specifically, it was an ID 10 T error. The worst part is that it was my fault. Can you spot the error?:
Protected Sub btnUpdate_Click(sender As Object, e As EventArgs) Handles btnUpdate.Click
End Sub
Protected Sub btnSelect_Click(sender As Object, e As EventArgs) Handles btnUpdate.Click
End Sub
I'm a little embarrassed that this was the reason for my lost morning. 
|
|
|
|
|
We have met the enemy and he is copy/paste.
|
|
|
|
|
You handled the wrong click event. I've never done that 
If it's not broken, fix it until it is
|
|
|
|
|
Never ever ever?? 
What about 3rd grade?! 
My programming get away... The Blog...
Taking over the world since 1371!
|
|
|
|
|
AspDotNetDev wrote: Can you spot the error?
I think it's pretty obvious...you're using VB
|
|
|
|
|
You must have been a VB6 programmer in the past, where methods were bound to events using method naming convention. VB.NET has the Handles keyword. My case was worse, back in the days when I was migrating from VB6 to VB.NET, I didn't even know that the Handles keyword exists and was wondering why my events were not getting fired. Now I avoid all these problem by writing code in C# :-p
|
|
|
|
|
AspDotNetDev wrote: Can you spot the error?
It's written in Visual basic (and I'd be embarrassed too).
But seriously, both methods handle the Click event from the Update button.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
Yes, it is VB.
(I didn't read the other responses because I am sure I am not the only one that said it)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
