Maybe you could use the difference between the Bounds and WorkingArea of the Screen object to locate the task bar.

S. Senthil Kumar wrote: I've seen the exception thrown when you are calling BeginInvoke on a control that has been instantiated but has not yet become visible. .NET 2.0 apparently creates the backing Win32 handle lazily, when the control is about to become visible for the first time, and if you happen to call Invoke/BeginInvoke before it, it fails with that error. This sounds very promising as the controls are indeed hidden -- do you know if this bug applies to .NET 3.5? Cheers, Greg

You're welcome. :) Luc Pattyn [Forum Guidelines] [My Articles] This month's tips: - before you ask a question here, search CodeProject, then Google; - the quality and detail of your question reflects on the effectiveness of the help you are likely to get; - use PRE tags to preserve formatting when showing multi-line code snippets.