When you delete an item in a list, any list, the indexes of the remaining items may change. There are two easy ways to cope with that: 1. not moving at all: assuming a range of items may have to be deleted, if the first item the be deleted is at index x, use RemoveAt(x); and continue testing for more removals at the same index x, as each removal there will decrement the index of all the # subsequent items by one. 2. working backwards: first determine the range to be deleted, without actually deleting anything; then delete from high index to low index; this also works when the items of interest aren't consecutive. Beware, whatever you choose to do, a foreach will fail as an enumerator becomes invalid (and will throw an exception) when the collection gets modified. :) Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] If you want my opinion or comment, ask in a forum or on my profile page; I will not participate in frackin' Q&A

Hi Daniel, I didnt have my opportunity to work with on screen keyboard. However I wanted to say that in my laptop whenever I have used my onscreen keyboard using mouse, I have always seen that it does not loose focus. So my opinion is that dont fear about the on screen keyboard and it "loosing focus" thing. You can do things as if you are using the actual keyboad. :) My post is not your reply however I wish it helps you. Thanks, Arindam D Tewary

Hi, I didn't look at your code as it was unformatted, lacking PRE tags. However I think you should read this[^]. :) Luc Pattyn Have a look at my entry for the lean-and-mean competition; please provide comments, feedback, discussion, and don’t forget to vote for it! Thank you. Local announcement (Antwerp region): Lange Wapper? Neen!

Shown should fire exactly once, the first time the form has become visible. MSDN: "Occurs whenever the form is first displayed." :) Luc Pattyn [Forum Guidelines] [My Articles] The quality and detail of your question reflects on the effectiveness of the help you are likely to get. Show formatted code inside PRE tags, and give clear symptoms when describing a problem.

You are suggesting a forms application with 3 physical tiers (client, server, database)? That is appropriate if you want to scale to large amounts of clients, or if you have specific security concerns. Otherwise, you should be aware that it is more expensive to build than a simpler 2-tier arrangement. (You should still logically split the application into layers). my blog

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemnetsocketstcplistenerclasstopic.asp