Hi Yossi,

>But - could you direct me to a source where I could get some info as what is happening here?

How much information do you want? *g*

The control is basically a COM server just like the ones you probably have used in VFP. If you have used Word automation, you created an instance of Word with CREATEOBJECT("Word.Application"). Same here. The strange syntax in the CMD file is a result of this control being written in .NET instead of VB or C++. It's doing the same thing that REGSVR32.EXE would do when you register an OCX.

x = new name.name

is nothing but the VB.NET equivalent of CREATEOBJECT() in VFP. You can safely ignore the part about the TLB file. That's what VFP takes care of internally. Those references are meant for VB6 where you have to add the TLB as a reference to the project. VFP loads those automatically at runtime. If you want to read about this difference, search the VFP help for early versus late binding. TLBs are needed for early binding, VFP does late binding by default.

Does that make sense, or do you need some more pointers to MSDN pages to read about the technical background of all this?