I think it's because .NET is truly object oriented and a string is an object.
Whereas it would not work in VBA because a string is not an object and so
when you try to do the assignment in VBA, it tells you that you need an
object to assign to another object... something like that...


--
Hope that helps.

Vergel Adriano


"akash" wrote:

Some more info:

I've extended the interface to include

Function GetValue() As Object
Sub SetValue(ByVal V As Object)

and I am able to do CC.SetValue("abcd"). This is even more puzzling,
as I thought .Net properties got converted to setter and getter
methods by the compiler, which is basically what I am replicating in
the above interface.

Akash