I am trying to implement code similar to that suggested by the article
at http://msdn.microsoft.com/msdnmag/issues/01/05/wss/ (see figure 6).
I originally found similar code in the book referenced at the end of
this article.

When I try to set a value for the property for the baseschema

(line of code from above article --->

recADO.Fields("urn:schemas-microsoft-com:exch-data:baseschema") _
        = aCustomSchema
)

I get an error.

When the code tests for field status (field.status) the return is 16
(field does not exist).

YET, if the code runs a For...Next loop through the Record.Fields
collection, the field appears with a value for Field.Name, Field.Type
= 0 and Field.Value is Empty.

Checking Field.Status just before the For..Next loop gives 16 (does not exist)
and checking Field.Status just after the For..Next loop give 16 (does
not exist), yet there it is in the Fields Collection as evidenced by
the loop output.

I have check my permissions on the Exchange Server folders, etc, and I
have given myself full control permissions on the appropriate
foleders. I am running Exchange Server 2000, SP3 and programming an
ASP file. I can access, assign values to, and update other fields that
have values just fine (ie, "DAV:comment").

I need to know where to look next for a solution to assigning a value
to this field and information in general about why is the field.status
coming up "does not exist" when I can see it in the For..Next loop
output.

Thanks.