A great suggestion, unfortunately it didn't work. Field() isn't actually an object collection, it seems. There's no further properties behind it.
As for adding the .Object. well, that got rid of the error message, but it didn't populate the fields with my values. The best part is, there is another ActiveX control that is used to return information about a template. It returns an object named Field with additional properties for each piece of information - that one works fine! Such as: elInfo.Field("COLOR").Size returns the number of characters in the field.
In the PEMs list for the first control, it simply lists FIELD(FieldName as String) AS String. That, plus the example code, leads me to believe that is used as simply as I am trying to use it. I'm already waiting on a reply from the vendor, but odds are pretty good they've never even heard of Visual Foxpro, or don't realize it still exists.

Randy


>I suppose that behind Field() collection there are some member you omitt, which VB automaticallu recognizes. Try to type point behind Fields() and see if IntelliSense will show some member like Value, etc. For example:
>
>

>thisform.elb1.Object.Field("PARTNO").Value = "123456"
>thisform.elb1.Object.Field("COLOR").Value = "Green"
>

>
>I also put "Object" in these rows; there are situations in VFP, in which this also was solve some problems.