nope, didn't help, i keep getting the same problem.... i have to do it this way, if i try to go with the return way on the handler, the textbox that i want to work on doesn't get the typed text...

Hi, the rule is to perform long (over 30 msec) operations on extra threads, and all GUI stuff on the main thread (because Controls are not thread-safe, so having other threads access some Controls will eventually hang the app). :) Luc Pattyn [Forum Guidelines] [My Articles] this weeks tips: - make Visual display line numbers: Tools/Options/TextEditor/... - show exceptions with ToString() to see all information - before you ask a question here, search CodeProject, then Google

hey Amjath, perhaps you have little misunderstanding of the question.;) to daniel, I think it's the question about how to bind key events in a simple way. As it mentioned above, there're too many child forms in the parent form, and you don't want to bind the key event in each child form. Thinking of this, if there's a base form called ControlEx (or something else), and it contains the override method of OnKeyPress, OnKeyUp, etc, things will be simpler when all the child forms inheritted from ControlEx not from System.Windows.Froms.UserControl. --------------------------------- Believe what you saw!

Sarafian wrote: The original question said about rows. Well, you don't always get what you ask for. :) Sarafian wrote: The only way I can think except from triggers is to have a column something like just updated. Then query for those and just before finishing set the columns to false. An alternative would be to first get the id:s of the records to update, then use them to update the records. --- Year happy = new Year(2007);

simple as that. thanx a lot :laugh: daniel

Great. Glad I could help! Steve