ADO library corruption

Is there any way to find out whether the ADO.Net library installed on the
Deployment PC is working fine. I am developing a workflow application using
Exchange server. I have defined some custom properties to folder in exchange
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. WorkflowSession.Fields)
it returns no value. The same functions are working fine on the developemnt
PC.

I feel the ADO.net library is not working properly. Is there a way to find
out?

Devesh Aggarwal

re: ADO library corruption

Hi devesh
check for ADO Library version on your exchnage PC.
it should be ADO 2.7
[color=blue]
>-----Original Message-----
>Is there any way to find out whether the ADO.Net library[/color]
installed on the[color=blue]
>Deployment PC is working fine. I am developing a workflow[/color]
application using[color=blue]
>Exchange server. I have defined some custom properties to[/color]
folder in exchange[color=blue]
>WSS. I am able to access them using exchange explorer.[/color]
But when i try to[color=blue]
>access the same value using ADO.net functions (e.g.[/color]
WorkflowSession.Fields)[color=blue]
>it returns no value. The same functions are working fine[/color]
on the developemnt[color=blue]
>PC.
>
>I feel the ADO.net library is not working properly. Is[/color]
there a way to find[color=blue]
>out?
>
>Devesh Aggarwal
>
>
>.
>[/color]

re: ADO library corruption

Hi,
MDAC 2.7 is already installed on machine.
i tried
workflowsession.addaudittrial workflowsession.fields.count
command.

this basically send the message to event viewer. this
gives a error message as Error No:8002801d. Description:
i searched this error on google. the outcome was library
not registered.

thz.[color=blue]
>-----Original Message-----
>Hi devesh
>check for ADO Library version on your exchnage PC.
>it should be ADO 2.7
>[color=green]
>>-----Original Message-----
>>Is there any way to find out whether the ADO.Net[/color][/color]
library[color=blue]
>installed on the[color=green]
>>Deployment PC is working fine. I am developing a[/color][/color]
workflow[color=blue]
>application using[color=green]
>>Exchange server. I have defined some custom properties[/color][/color]
to[color=blue]
>folder in exchange[color=green]
>>WSS. I am able to access them using exchange explorer.[/color]
>But when i try to[color=green]
>>access the same value using ADO.net functions (e.g.[/color]
>WorkflowSession.Fields)[color=green]
>>it returns no value. The same functions are working[/color][/color]
fine[color=blue]
>on the developemnt[color=green]
>>PC.
>>
>>I feel the ADO.net library is not working properly. Is[/color]
>there a way to find[color=green]
>>out?
>>
>>Devesh Aggarwal
>>
>>
>>.
>>[/color]
>.
>[/color]

re: ADO library corruption

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 works
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 Experts
http://www.cdolive.com

This information is provided "AS IS" with no warranties, and confers no
rights.
You assume all risk for your use. © 2003 CDOLive LLC. All rights reserved.
Sample code subject to http://www.cdolive.com/disclaim.htm

"Devesh Aggarwal" <solutions@unieme.com> wrote in message:[color=blue]
>
> Is there any way to find out whether the ADO.Net library installed on the
> Deployment PC is working fine. I am developing a workflow application[/color]
using[color=blue]
> Exchange server. I have defined some custom properties to folder in[/color]
exchange[color=blue]
> 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.[/color]
WorkflowSession.Fields)[color=blue]
> it returns no value. The same functions are working fine on the[/color]
developemnt[color=blue]
> PC.
>
> I feel the ADO.net library is not working properly. Is there a way to find
> out?
>
> Devesh Aggarwal[/color]

re: ADO library corruption

I made a mistake in my earlier message. It is not ADO.Net but ADODB function

Devesh
"Siegfried Weber [MVP]" <info@cdolive.com> wrote in message
news:#p3PvS3RDHA.2228@tk2msftngp13.phx.gbl...[color=blue]
> 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[/color]
works[color=blue]
> 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[/color]
Experts[color=blue]
> http://www.cdolive.com
>
> This information is provided "AS IS" with no warranties, and confers no
> rights.
> You assume all risk for your use. © 2003 CDOLive LLC. All rights reserved.
> Sample code subject to http://www.cdolive.com/disclaim.htm
>
> "Devesh Aggarwal" <solutions@unieme.com> wrote in message:[color=green]
> >
> > Is there any way to find out whether the ADO.Net library installed on[/color][/color]
the[color=blue][color=green]
> > Deployment PC is working fine. I am developing a workflow application[/color]
> using[color=green]
> > Exchange server. I have defined some custom properties to folder in[/color]
> exchange[color=green]
> > 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.[/color]
> WorkflowSession.Fields)[color=green]
> > it returns no value. The same functions are working fine on the[/color]
> developemnt[color=green]
> > PC.
> >
> > I feel the ADO.net library is not working properly. Is there a way to[/color][/color]
find[color=blue][color=green]
> > out?
> >
> > Devesh Aggarwal[/color]
>[/color]