Problem with ADO

Hello,
First of all, excuse me for my very poor english : I just "speak" a bit of
english...
We recently have a problem with some PCs and ADO : we can connect our
programs to databases (SqlServer 2000 or Express 2005) via ADO.Net or ODBC,
but it doesn't work via ADO !? PCs are under Windows 2000 or Windows XP
(SP2). Our programs written in C# or VB.Net which use ADO.Net work perfectly
with the databases. But our programs written in "old" VB6 can't connect to
the same
database on the same computer (*) It's not the case for all the PCs, just
for a small minority... For these minority, the problem concerns third
partie products too... And with XP SP2, whe can't try to reinstall MDAC,
because Windows rejects the reinstall...
Any idea ?
Thanx in advance !!!
(*) We are sure it isn't a problem of connect string, you can forget this
reason ;-)Try to use the OLE DB native provider for SQL Server. In this case the MDAC
stack is not required. See SNAC or "SQL Server Native Client" in online help
. It's designed to access SQL Server 2005 instances and all of their new fea
tures.
I would also use the Component Checker tool (downloadable from here). It wou
ld also help to review this.
Clearly, the reason some computers can connect and others cannot is a differ
ence in the systems... ;) The Component Checker can show the differences in
the myriad of MDAC layered components installed. This problem is (partially)
alleviated with the SNAC provider.
I discuss these issues in my book "ADO.NET Examples and Best Practices".
hth
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"News" <news@.invalid> wrote in message news:466d1e93$0$28887$426a34cc@.news.free.fr...seagreen">
> Hello,
>
> First of all, excuse me for my very poor english : I just "speak" a bit of
> english...
>
> We recently have a problem with some PCs and ADO : we can connect our
> programs to databases (SqlServer 2000 or Express 2005) via ADO.Net or ODBC
,
> but it doesn't work via ADO !? PCs are under Windows 2000 or Windows XP
> (SP2). Our programs written in C# or VB.Net which use ADO.Net work perfect
ly
> with the databases. But our programs written in "old" VB6 can't connect to
> the same
> database on the same computer (*) It's not the case for all the PCs, just
> for a small minority... For these minority, the problem concerns third
> partie products too... And with XP SP2, whe can't try to reinstall MDAC,
> because Windows rejects the reinstall...
>
> Any idea ?
>
> Thanx in advance !!!
>
> (*) We are sure it isn't a problem of connect string, you can forget this
> reason ;-)
>
>
>|||It works with SNAC !
Thank you for your help !
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> a crit dans le message
de news: eVugpLErHHA.5032@.TK2MSFTNGP02.phx.gbl...
Try to use the OLE DB native provider for SQL Server. In this case the MDAC
stack is not required. See SNAC or "SQL Server Native Client" in online help
. It's designed to access SQL Server 2005 instances and all of their new fea
tures.
I would also use the Component Checker tool (downloadable from here). It wou
ld also help to review this.
Clearly, the reason some computers can connect and others cannot is a differ
ence in the systems... ;) The Component Checker can show the differences in
the myriad of MDAC layered components installed. This problem is (partially)
alleviated with the SNAC provider.
I discuss these issues in my book "ADO.NET Examples and Best Practices".
hth
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"News" <news@.invalid> wrote in message news:466d1e93$0$28887$426a34cc@.news.free.fr...seagreen">
> Hello,
>
> First of all, excuse me for my very poor english : I just "speak" a bit of
> english...
>
> We recently have a problem with some PCs and ADO : we can connect our
> programs to databases (SqlServer 2000 or Express 2005) via ADO.Net or ODBC
,
> but it doesn't work via ADO !? PCs are under Windows 2000 or Windows XP
> (SP2). Our programs written in C# or VB.Net which use ADO.Net work perfect
ly
> with the databases. But our programs written in "old" VB6 can't connect to
> the same
> database on the same computer (*) It's not the case for all the PCs, just
> for a small minority... For these minority, the problem concerns third
> partie products too... And with XP SP2, whe can't try to reinstall MDAC,
> because Windows rejects the reinstall...
>
> Any idea ?
>
> Thanx in advance !!!
>
> (*) We are sure it isn't a problem of connect string, you can forget this
> reason ;-)
>
>
>|||Thanks for letting us know. I'll send you a bill. ;)
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"News" <news@.invalid> wrote in message news:466e8f95$0$14995$426a34cc@.news.f
ree.fr...
It works with SNAC !
Thank you for your help !
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> a crit dans le message
de news: eVugpLErHHA.5032@.TK2MSFTNGP02.phx.gbl...
Try to use the OLE DB native provider for SQL Server. In this case the MDAC
stack is not required. See SNAC or "SQL Server Native Client" in online help
. It's designed to access SQL Server 2005 instances and all of their new fea
tures.
I would also use the Component Checker tool (downloadable from here). It wou
ld also help to review this.
Clearly, the reason some computers can connect and others cannot is a differ
ence in the systems... ;) The Component Checker can show the differences in
the myriad of MDAC layered components installed. This problem is (partially)
alleviated with the SNAC provider.
I discuss these issues in my book "ADO.NET Examples and Best Practices".
hth
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"News" <news@.invalid> wrote in message news:466d1e93$0$28887$426a34cc@.news.free.fr...seagreen">
> Hello,
>
> First of all, excuse me for my very poor english : I just "speak" a bit of
> english...
>
> We recently have a problem with some PCs and ADO : we can connect our
> programs to databases (SqlServer 2000 or Express 2005) via ADO.Net or ODBC
,
> but it doesn't work via ADO !? PCs are under Windows 2000 or Windows XP
> (SP2). Our programs written in C# or VB.Net which use ADO.Net work perfect
ly
> with the databases. But our programs written in "old" VB6 can't connect to
> the same
> database on the same computer (*) It's not the case for all the PCs, just
> for a small minority... For these minority, the problem concerns third
> partie products too... And with XP SP2, whe can't try to reinstall MDAC,
> because Windows rejects the reinstall...
>
> Any idea ?
>
> Thanx in advance !!!
>
> (*) We are sure it isn't a problem of connect string, you can forget this
> reason ;-)
>
>
>