|
|
You're in the
sql server connect
group:Problem with ADO
sql server connect:
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 features.=20 I would also use the Component Checker tool (downloadable from here). It = would also help to review this. Clearly, the reason some computers can connect and others cannot is a = difference 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 --=20 ____________________________________ 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) -------------------------------------------------------------------------= ---------------------------------------------- [quoted text, click to view] "News" <news@invalid> wrote in message =
news:466d1e93$0$28887$426a34cc@news.free.fr... > Hello, >=20 > First of all, excuse me for my very poor english : I just "speak" a = bit of=20 > english... >=20 > We recently have a problem with some PCs and ADO : we can connect our=20 > programs to databases (SqlServer 2000 or Express 2005) via ADO.Net or = ODBC,=20 > but it doesn't work via ADO !? PCs are under Windows 2000 or Windows = XP=20 > (SP2). Our programs written in C# or VB.Net which use ADO.Net work = perfectly=20 > with the databases. But our programs written in "old" VB6 can't = connect to=20 > the same > database on the same computer (*) It's not the case for all the PCs, = just=20 > 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,=20 > because Windows rejects the reinstall... >=20 > Any idea ? >=20 > Thanx in advance !!! >=20 > (*) We are sure it isn't a problem of connect string, you can forget = this=20 > reason ;-) >=20 >=20
It works with SNAC !
Thank you for your help ! "William (Bill) Vaughn" <billvaRemoveThis@betav.com> a =E9crit 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 features.=20 I would also use the Component Checker tool (downloadable from here). = It would also help to review this. Clearly, the reason some computers can connect and others cannot is a = difference 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 --=20 ____________________________________ 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) = -------------------------------------------------------------------------= ---------------------------------------------- [quoted text, click to view] "News" <news@invalid> wrote in message =
news:466d1e93$0$28887$426a34cc@news.free.fr... > Hello, >=20 > First of all, excuse me for my very poor english : I just "speak" a = bit of=20 > english... >=20 > We recently have a problem with some PCs and ADO : we can connect = our=20 > programs to databases (SqlServer 2000 or Express 2005) via ADO.Net = or ODBC,=20 > but it doesn't work via ADO !? PCs are under Windows 2000 or Windows = XP=20 > (SP2). Our programs written in C# or VB.Net which use ADO.Net work = perfectly=20 > with the databases. But our programs written in "old" VB6 can't = connect to=20 > the same > database on the same computer (*) It's not the case for all the PCs, = just=20 > for a small minority... For these minority, the problem concerns = third=20 > partie products too... And with XP SP2, whe can't try to reinstall = MDAC,=20 > because Windows rejects the reinstall... >=20 > Any idea ? >=20 > Thanx in advance !!! >=20 > (*) We are sure it isn't a problem of connect string, you can forget = this=20 > reason ;-) >=20 >=20
Thanks for letting us know. I'll send you a bill. ;)
--=20 ____________________________________ 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) -------------------------------------------------------------------------= ---------------------------------------------- [quoted text, click to view] "News" <news@invalid> wrote in message = It works with SNAC !news:466e8f95$0$14995$426a34cc@news.free.fr... Thank you for your help ! "William (Bill) Vaughn" <billvaRemoveThis@betav.com> a =E9crit 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 features.=20 I would also use the Component Checker tool (downloadable from = here). It would also help to review this. Clearly, the reason some computers can connect and others cannot is = a difference 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 --=20 ____________________________________ 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) = -------------------------------------------------------------------------= ---------------------------------------------- [quoted text, click to view] "News" <news@invalid> wrote in message =
news:466d1e93$0$28887$426a34cc@news.free.fr... > Hello, >=20 > First of all, excuse me for my very poor english : I just "speak" = a bit of=20 > english... >=20 > We recently have a problem with some PCs and ADO : we can connect = our=20 > programs to databases (SqlServer 2000 or Express 2005) via ADO.Net = or ODBC,=20 > but it doesn't work via ADO !? PCs are under Windows 2000 or = Windows XP=20 > (SP2). Our programs written in C# or VB.Net which use ADO.Net work = perfectly=20 > with the databases. But our programs written in "old" VB6 can't = connect to=20 > the same > database on the same computer (*) It's not the case for all the = PCs, just=20 > for a small minority... For these minority, the problem concerns = third=20 > partie products too... And with XP SP2, whe can't try to = reinstall MDAC,=20 > because Windows rejects the reinstall... >=20 > Any idea ? >=20 > Thanx in advance !!! >=20 > (*) We are sure it isn't a problem of connect string, you can = forget this=20 > reason ;-) >=20 >=20
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |