Just pass it like this: myClassTwo.FunctionOne(p_MyObject); myClassThree.FunctionOne(p_MyObject); Your functions are accepting pointers, and the object you're passing is a pointer. There is no need to dereference it. "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997 ----- "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001

To add to what Mike says, the objects that you add to the hash table are also managed objects, and thus garbage collected. If you add unmanaged pointers to the hashtable, you'd have to manually delete the native objects that are pointed to by those pointers. My blog : Nish’s thoughts on MFC, C++/CLI and .NET

Try posting this as a new question in the forum so that others can also look at it. -Prakash

Try this: Catch ex As ThreadAbortException Trace.WriteLine("READ THREAD ABORT EXCEPTION!") 'Allow the thread to continue aborting: Thread.ResetAbort() david

Thanks!

Hai Nothing wrong in ur code. i also don't know why it happened. But placing your second class before the Form1 calss will solve the problem. ie define all your classes before it uses by Anisg

That worked great!! I had no idea I could do it like that. That opens up all sorts of possiblities for me :-D Thank you very much for taking the time to help me out! Jody Blau

You can create an event where-ever you like, so long as the object defines the event, or you're writing or wrapping the object in order to cause it to fire. For example, if you write a class that encapsulates a hash table, you can define an event that your class will fire, but I don't believe that hash tables define such an event. Christian I have drunk the cool-aid and found it wan and bitter. - Chris Maunder