Click here to Skip to main content
15,892,537 members

Comments by Ivan_FM (Top 19 by date)

Ivan_FM 16-Apr-16 5:08am View    
Really thanks for sharing you knowledge OrignalGriff!
Ivan_FM 11-Apr-16 7:24am View    
Ok, try this again. I've just tried it right now and Works fine.

Private Sub TextBox1_KeyDown(sender As Object, e As KeyEventArgs) Handles TextBox1.KeyDown
Select Case e.KeyCode
Case Keys.Enter
e.SuppressKeyPress = True
End Select
End Sub

Because the textbox has multiline=false, you can supress this key and there's no problem. Also you can convert the "Enter" kepress to a "TAB" adding it to the case if you want.
Ivan_FM 11-Apr-16 5:03am View    
Yes, I've been working with this, changing all in order to work only with one procedure. Really more optimized, also in the app code! ;) It's really a better way to do it. Thanks!
Ivan_FM 10-Apr-16 12:53pm View    
Ok OriginalGriff, I've tried it and Works fine. Realy great! ;)

But there's one question... when i do this in two separate procedures i can see easilly from where the issues comes. If i do INSERT and UPDATE with the same procedure, how can i know wich part have the issue?
Ivan_FM 10-Apr-16 7:54am View    
The "IF @@ROWCOUNT = 0" Works like the "if exist"? Wow, nice point! I will use this in order to use only one stored procedure to insert and update rows. I will try it now, thanks!!