What classic ADO version are you running on this computer? Can you make sure
the account used to run the workflow has proper access to the data? Can you
access any other field in the Workflowsession.Fields collection? What state
is the workflow in when you are trying to access the field? Might be too
early to get your hands on the data.
<Cheers:Siegfried runat="server" />
CDOLive LLC - The Microsoft Messaging and Collaboration Application Experts
This information is provided "AS IS" with no warranties, and confers no
You assume all risk for your use. ? 2003 CDOLive LLC. All rights reserved.
Sample code subject to http://www.cdolive.com/disclaim.htm
> I made a mistake in my earlier message. It is not ADO.Net but ADODB
>> I believe your problem is a result of the fact that there is no ADO.NET
>> provider to access Exchange. There is an Exchagne OLEDB provider which
>> only with classic ADO and the Internet Publishing Provider (MSDAIPP.DSO)
>> which also is only with classic ADO supported.
>> <Cheers:Siegfried runat="server" />
>> Development Lead,
>> CDOLive LLC - The Microsoft Messaging and Collaboration Application
>> This information is provided "AS IS" with no warranties, and confers no
>> You assume all risk for your use. ? 2003 CDOLive LLC. All rights
>> Sample code subject to http://www.cdolive.com/disclaim.htm
>>> Is there any way to find out whether the ADO.Net library installed on
>>> Deployment PC is working fine. I am developing a workflow application
>>> Exchange server. I have defined some custom properties to folder in
>>> WSS. I am able to access them using exchange explorer. But when i try to
>>> access the same value using ADO.net functions (e.g.
>>> it returns no value. The same functions are working fine on the
>>> I feel the ADO.net library is not working properly. Is there a way to
>>> Devesh Aggarwal