Gareth, If you get anywhere with this solution, please drop a line here on the message board. I'd be intrigued to see what happens. Thanks. Curtis. "we must lose precision to make significant statements about complex systems." -deKorvin on uncertainty

The solution will work if there only a few signatures. You just need to create one WrapperDelegate for each type and add one executeFunction for each such WrapperDelegate. Regards Senthil _____________________________ My Blog | My Articles | WinMacro

Gareth_Hastings wrote: Set MyDCOM = CreateObject("NODMON.NODCLS") retval = MyDCOM.addmsg("", "", 1, Now, 0, 3000, Message) What you are doing here is late binding in VB. While C# does support late-bound object creation (i.e.; look at Activator.CreateInstance), there are several ways to access what you are doing. One is to generate the appropriate interop assemblies (for example if you are using Visual Studio .NET you can simply use the Add Reference -> COM tab), this will allow you to declare the object and take advantage of early-binding at compile-time or you could use reflection to generate the object at run-time (the Activator class). - Nick Parker My Blog | My Articles

If you are looking for the syntax of classes for C#, the following is a simple example: public class TrafficLight { // constructor TrafficLight(){} // private variable private Color \_color; // public property public Color LightColor { get{return \_color;} set{\_color = value;} } public virtual void ChangeColor(Color newColor) { LightColor = newColor; } } public class DeluxeLight : TrafficLight { // constructor DeluxeLight(){} public overrides void ChangeColor(Color myColor) { //.... overriding the base class method } } - Nick Parker   My Blog