Going on the little info you provided us <we are NOT in your head -- you have to explain your problems better> is that you are making an active x reference to the CDO object, and it's attempting to put a JavaActiveX wrapper around it in order to play by the rules of COM.<BR><BR>Just do Server.CreateObject instead... don't 'install the cdo.dll manually'
Read her/his posts from down below. This person has more problems with CDO then I've ever seen.<BR><BR>This is an extension of a post from earlier today.<BR><BR>I've noticed that if she/he doesn't get a response in about an hour, they repost phrasing the question slightly different.<BR><BR>-Doug
My entire problem is that i have a windows2000 server and i would like to use cdo object, but the dll is not install by default whith windows 2000 server.<BR>This morning someone tell me to install manually cdo.dll and generate the wrapper.<BR>but my problem is that i would use de CDO object in a ASP page ant the error that i have is "Item cannot be found in the collection corresponding to the requested name or ordinal" for the first property that i use.
When you say 'manually', what do you mean? Shouldn't you just put the dll in your System32 and let ASP call it?<BR><BR>Something tells me you're using InterDev and forcefully creating the reference to it?<BR><BR>Are you *sure* this dll is a COM object?
manually : i put the dll on the server and register it ...<BR>but i have this error :<BR>*ADODB.Fields (0x800A0CC1)<BR>*Item cannot be found in the collection corresponding to the *requested name or ordinal.<BR><BR>yes im sure this is a COM object.<BR>