> Has anyone out there noticed that a VB property field
> which accepts/returns an object is problematic when used
> in a Windows Control library?

> i.e.

> Public ReadOnly Property DateObject() As EBFDate
>     Get
>     End Get
> End Property

> produces an error for me when(presumably because it is
> trying to instantiate the object????  when I drag an
> instance of the control onto a form.

> whereas the following works fine

> Public Function DateObject() As EBFDate
> End Function

> This looks like a bug.