Very Computer

However this code:
<%
set x = Server.CreateObject("ADODB.Connection")
Response.Write "ADO Version: " & x.Version & "<br>"
%>
returns ADO Version: 2.7

So which is it: the Version property returns 2.7, while I can't explicitly
create a 2.7 object.

Thank you,

-Tom.

I think you would need to use ADODB.Connection syntax to open connection. In
that case it will open connection based on latest installed version of ADO.
Otherwise you could depend on version

--
Val Mazur
Microsoft MVP

Quote:> I have an ActiveX DLL the manufacturer tells me uses ADO 2.7.
> I was able to convince my ISP to run MDAC 2.7.
> Before that, I was able to create an object of type ADODB.Connection.2.5
> After the upgrade, I can still do that, but I cannot create an object of
> type ADODB.Connection.2.7:
> <%
> set x = Server.CreateObject("ADODB.Connection.2.7")
> Response.Write "Creating ADODB.Connection.2.7 object: " & IsObject(x) &
> "<br>"
> %>
>  If I try, I get this error:
> Server object error 'ASP 0177 : 800401f3'
> Server.CreateObject Failed
> /test_ado.asp, line 11
> Invalid ProgID. For additional information specific to this message please
> visit the Microsoft Online Support site located at:
> http://www.microsoft.com/contentredirect.asp.

> However this code:
> <%
> set x = Server.CreateObject("ADODB.Connection")
> Response.Write "ADO Version: " & x.Version & "<br>"
> %>
> returns ADO Version: 2.7

> So which is it: the Version property returns 2.7, while I can't explicitly
> create a 2.7 object.

> Thank you,

> -Tom.

This is almost certainly a registry issue.  Take a look at
HKEY_CLASSES_ROOT\ADODB.Connection and
HKEY_CLASSES_ROOT\ADODB.Connection.2.7.  If you don't have the latter,
there's your answer right there.  If you do have both, and both have the
same CLSID, then it may be a permissions issue on a registry key, probably
in HKEY_CLASSES_ROOT\TypeLib.

HTH,
Nicole

Quote:> I have an ActiveX DLL the manufacturer tells me uses ADO 2.7.
> I was able to convince my ISP to run MDAC 2.7.
> Before that, I was able to create an object of type ADODB.Connection.2.5
> After the upgrade, I can still do that, but I cannot create an object of
> type ADODB.Connection.2.7:
> <%
> set x = Server.CreateObject("ADODB.Connection.2.7")
> Response.Write "Creating ADODB.Connection.2.7 object: " & IsObject(x) &
> "<br>"
> %>
>  If I try, I get this error:
> Server object error 'ASP 0177 : 800401f3'
> Server.CreateObject Failed
> /test_ado.asp, line 11
> Invalid ProgID. For additional information specific to this message please
> visit the Microsoft Online Support site located at:
> http://www.microsoft.com/contentredirect.asp.

> However this code:
> <%
> set x = Server.CreateObject("ADODB.Connection")
> Response.Write "ADO Version: " & x.Version & "<br>"
> %>
> returns ADO Version: 2.7

> So which is it: the Version property returns 2.7, while I can't explicitly
> create a 2.7 object.

> Thank you,

> -Tom.

Quote:> I have an ActiveX DLL the manufacturer tells me uses ADO 2.7.
> I was able to convince my ISP to run MDAC 2.7.
> Before that, I was able to create an object of type ADODB.Connection.2.5
> After the upgrade, I can still do that, but I cannot create an object of
> type ADODB.Connection.2.7:

The whole point is that if people want to use "the latest version of the
connection object", they can. It has no numeral.

The chances are you had MDAC 2.6 installed before.

Stephen Howe

I disagree. On two of my own computers (both win2000pro, everything up to
date) I can create the 2.5, 2.6, 2.7, and <none> versions of
ADODB.Connection. The latter's Version property shows 2.7
However at my ISP I can create 2.5 and <none>, with the latter's Version
property shows 2.7

I'm leaning towards Nicole's suggestion that somehow the ISP's installation
is corrupt. I'm going to ask them to run Component Checker to verify this.

-Tom.

Quote:> Hi Stephen,

> I disagree.

Quote:> I'm leaning towards Nicole's suggestion that somehow the ISP's
installation
> is corrupt. I'm going to ask them to run Component Checker to verify this.

Stephen Howe