What Stefan is saying is that you need to use the Invoke method on the parent control in order to call Form.Show. See the method documentation for Invoke in the .NET Framework SDK for more information. Microsoft MVP, Visual C# My Articles

here's the solution: http://www.banasoft.net/AVPhone.htm

Try closing the connection object before you check the output parameter value. I haven't the faintest idea why, but with sql7.0 I get null for output parameters until after I call the close method on the connections... Someone smarter than I will have to take a shot at why that might be... Grasping... Bill

You'll need a file system driver that monitors file system device objects for IRPs and FastIO requests directed at the drives on your computer. "The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)

You should look into Windows Hooks[^]. C# is really not the best language for this. C/C++ would be better suited for something that needs to be fast and may or may not load in-proc with other applications. For more information on Windows Hooks, see Hooks[^] in the Platform SDK. Microsoft MVP, Visual C# My Articles

Try this and this. A rich person is not the one who has the most, but the one that needs the least.

There's always the topics in the .NET Framework SDK, which is always a good place to start: http://msdn.microsoft.com/library/en-us/cpguide/html/cpconCOMRegularExpressions.asp[^]. -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----

NUnit 2.1[^] --Colin Mackay-- EuroCPian Spring 2004 Get Together[^]

This is the behavior of the ComboBox common control, which the System.Windows.Forms.ComboBox class wraps. In order to override this sort of functionality, you should read about the ComboBox common control (in the "User Interface Design and Development" section of MSDN, under "Windows Controls") and extend the ComboBox class in .NET in order to override the WndProc method and handle the notification messages yourself. Some of this might be possible using managed events, but not everything always is. -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----

Ooh, here's a topic I love to tear apart! Make sure you actually know what you're talking about before getting certified. Sure, it looks good on resumes but if you don't know what you're talking about and tout your certifications to people that do, you not only look like an idiot but make certifications look bad. Personally, I am not certified because I really don't want to be. I know a large number of people with certifications that know crap. They studied for the tests, memorized a few things, took the tests (sometimes a couple times) and got their certs. They're still idiots. That's not to say certifications are bad. Like I said, they do look good on resumes (the only reason I might someday do it if I have time...I already have the material and study books) and can up your salary at hire-time (or even at a current job if you work for that kind of company). Just make sure you have the knowledge to back it up! That being said, you can also get your MCSD. Take the MCADs and pay attention to the courses you take. Take a look at the MCSDs and you'll find that MCAD - with the right courses - is a subset of MCSDs. There's only like a couple more tests you have to take if you take the subset of courses that get you your MCAD. Good luck! -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----

AppDomain.UnhandledException You can get the current AppDomain with AppDomain.Current. -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----

Handle the HttpApplication.Error event in your Global.asax file, or it's related code-behind file. Since auto-event-writeup is enabled by default, you can just declare your handler as private void Application_Error(object sender, EventArgs e) { HttpServerUtility server = HttpContext.Current.Server Exception e = server.GetLastError(); // ... } For more information, see the documentation for the event I mentioned, and the HttpServerUtility.GetLastError method. You could also create your own IHttpModule for handling, errors, too, if you require library portability without moving the whole web application. -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----