You're not missing anything, it's me having had to little coffee and a non-functional brain. Sorry 'bout that. Be excellent to each other. And... PARTY ON, DUDES! Abraham Lincoln

Thanks, I'll definitely look into message queues also. Of course you're right as regards TCP/IP being full duplex. My misunderstanding comes from the typical way in which I've always been used to implementing the application layer protocol on top of the TCP layer. In it's most basic form TCP comms consist basically of two streams, one upstream and one downstream. The server can put any message at any time into the downstream while the client can put any message at any time into the upstream. So yes, that is the textbook definition of full duplex. What makes WCF more suitable to me (I think) is the fact that the implementation of all this seems to be much easier. With TCP, I'd have to write a thread that constantly reads the downstream and decide what is a response to a message that was sent on the upstream and what is a message that simply arrives unsolicited. With WCF the response to an upstream message comes in the form of a return value to the function that is called while an unsolicited message comes in the form of a callback function that is called.

Goodness! I didn't even notice there was a forum dedicated to WCF. Thanks for pointing out.

No, I believe that works only for Webforms, not for Winforms as is the case here. I don't understand why that method is not available in winforms as it would have been the perfect solution for this problem of mine.

BobJanova wrote: This is true but buttons and menu items still fire 'click' events even if you select them with the keyboard (and, personally, I'd recommend you do this with any custom controls you write that have an action on click, too). Yup - but I still see a lot of buttons that only react on their Control.MouseClick event - just wanted to touch the subject to ensure that it's not overlooked :) Bastard Programmer from Hell :suss:

Sub queries are run in a temporary memory space, hence they can be slower. However, most engines now are capable of converting sub queries into INs, so in general for new databases, you should be ok with both.

yap it will work

Database Engine Tuning Advisor[^] might be of help.

dear dewald try this order display member value member datasource i hope it help you

Excellent. Thanks for the help. That is exactly what I was looking for.

No, it's not. It's entirely possible to have a form deactived, but the focus never really leaves the confines of the form. I know, it's rare, but it happens... It's also possible to have the focus leave the form, but never deactivate the form by clicking on someone outside of it. What you do with those events is up to you. A guide to posting questions on CodeProject[^] Dave Kreskowiak

Thanks, it looks interesting, but jeeeez, it looks complicated. I'll go through it more attentively when I have a little more time but, briefly, could you explain why that method is better than using a DataSet like in my earlier example?

LOL. Minority Report UI based on Kinect, that is too funny! I've had some outlandish requests from users but this one takes the biscuit.

That is perfect, thanks! That is exactly what I should have been doing from the very start.

Had a little play now.. are your items all the same type? i.e. ToolStripButton as you can create all those controls. This is pretty messy but just an idea of what I was playing with... foreach (ToolStripItem item in toolStripDropDownButton1.DropDownItems) { ToolStripItem newItem = new ToolStripMenuItem(); if (item is ToolStripComboBox) newItem = new ToolStripComboBox(); else if (item is ToolStripTextBox) newItem = new ToolStripTextBox(); newItem.Text = item.Text; toolStripDropDownButton2.DropDownItems.Add(newItem); } return 5;

Dankie Kwagga, I've never actually used a DataAdapter, I don't know why. So I'll definitely give this a try, thanks.

This Link[^] may help you to get some idea