VB & Database, Upgrading connection to SQL Server 2000 from vb6

Upgrading connection to SQL Server 2000 from vb6

Author	Message
Lisa #1 / 8	Upgrading connection to SQL Server 2000 from vb6 I have avb6 application running on Windows NT connecting to SQL Server 7, and all is fine. We have upgraded to Windows 2000 Server ans SQL2000. This is fine and the SQL Server is running. I have changed the connection string in the VBapp to connect to the new server, but the application will not run. The error being generated by VB6 is on the connection open line, and just gives "Client is unable to establish connection" The Windows2000 server is available on the network. Do I need an upgraded driver?? Any help gratefully received Thanks
Fri, 27 Jun 2003 21:07:01 GMT

Dennis Redfiel #2 / 8	Upgrading connection to SQL Server 2000 from vb6 shouldn't need to update the driver - but it is a GOOD thing to do. Better to post the connections string here for us to look at. Quote: > I have avb6 application running on Windows NT connecting to SQL Server 7, > and all is fine. > We have upgraded to Windows 2000 Server ans SQL2000. This is fine and the > SQL Server is running. > I have changed the connection string in the VBapp to connect to the new > server, but the application will not run. The error being generated by VB6 > is on the connection open line, and just gives > "Client is unable to establish connection" > The Windows2000 server is available on the network. > Do I need an upgraded driver?? > Any help gratefully received > Thanks
Fri, 27 Jun 2003 21:53:15 GMT

Lisa #3 / 8	Upgrading connection to SQL Server 2000 from vb6 The connection string is driver=SQL Server;server=Global2ksvr;database=ni Connecting using windows log-ons. Works fine for old server Global, but not to new one. Quote: > shouldn't need to update the driver - but it is a GOOD thing to do. Better > to post the connections string here for us to look at. > > I have avb6 application running on Windows NT connecting to SQL Server 7, > > and all is fine. > > We have upgraded to Windows 2000 Server ans SQL2000. This is fine and the > > SQL Server is running. > > I have changed the connection string in the VBapp to connect to the new > > server, but the application will not run. The error being generated by VB6 > > is on the connection open line, and just gives > > "Client is unable to establish connection" > > The Windows2000 server is available on the network. > > Do I need an upgraded driver?? > > Any help gratefully received > > Thanks
Fri, 27 Jun 2003 23:50:42 GMT

Drew Montgomer #4 / 8	Upgrading connection to SQL Server 2000 from vb6 Assuming you are using ADO you should try using the oledb connect string something like this: Provider=sqloledb;Data Source=Global2ksvr;Initial Catalog=ni;User Id=xx;Password=yy xx is the login id for the server and yy is your password Hope this helps. Drew Quote: > The connection string is > driver=SQL Server;server=Global2ksvr;database=ni > Connecting using windows log-ons. > Works fine for old server Global, but not to new one. > > shouldn't need to update the driver - but it is a GOOD thing to do. > Better > > to post the connections string here for us to look at. > > > I have avb6 application running on Windows NT connecting to SQL Server > 7, > > > and all is fine. > > > We have upgraded to Windows 2000 Server ans SQL2000. This is fine and > the > > > SQL Server is running. > > > I have changed the connection string in the VBapp to connect to the new > > > server, but the application will not run. The error being generated by > VB6 > > > is on the connection open line, and just gives > > > "Client is unable to establish connection" > > > The Windows2000 server is available on the network. > > > Do I need an upgraded driver?? > > > Any help gratefully received > > > Thanks
Sat, 28 Jun 2003 04:35:22 GMT

Lisa #5 / 8	Upgrading connection to SQL Server 2000 from vb6 Still getting an error: Connection open (create file()) Any more suggetions? Thanks Quote: > Assuming you are using ADO you should try using the oledb connect string > something like this: > Provider=sqloledb;Data Source=Global2ksvr;Initial Catalog=ni;User > Id=xx;Password=yy > xx is the login id for the server and yy is your password > Hope this helps. > Drew > > The connection string is > > driver=SQL Server;server=Global2ksvr;database=ni > > Connecting using windows log-ons. > > Works fine for old server Global, but not to new one. > > > shouldn't need to update the driver - but it is a GOOD thing to do. > > Better > > > to post the connections string here for us to look at. > > > > I have avb6 application running on Windows NT connecting to SQL Server > > 7, > > > > and all is fine. > > > > We have upgraded to Windows 2000 Server ans SQL2000. This is fine and > > the > > > > SQL Server is running. > > > > I have changed the connection string in the VBapp to connect to the > new > > > > server, but the application will not run. The error being generated by > > VB6 > > > > is on the connection open line, and just gives > > > > "Client is unable to establish connection" > > > > The Windows2000 server is available on the network. > > > > Do I need an upgraded driver?? > > > > Any help gratefully received > > > > Thanks
Sat, 28 Jun 2003 17:52:07 GMT

Drew Montgomer #6 / 8	Upgrading connection to SQL Server 2000 from vb6 Are you using ADO 2.5? If not upgrade. Drew Quote: > Still getting an error: > Connection open (create file()) > Any more suggetions? > Thanks > > Assuming you are using ADO you should try using the oledb connect string > > something like this: > > Provider=sqloledb;Data Source=Global2ksvr;Initial Catalog=ni;User > > Id=xx;Password=yy > > xx is the login id for the server and yy is your password > > Hope this helps. > > Drew > > > The connection string is > > > driver=SQL Server;server=Global2ksvr;database=ni > > > Connecting using windows log-ons. > > > Works fine for old server Global, but not to new one. > > > > shouldn't need to update the driver - but it is a GOOD thing to do. > > > Better > > > > to post the connections string here for us to look at. > > > > > I have avb6 application running on Windows NT connecting to SQL > Server > > > 7, > > > > > and all is fine. > > > > > We have upgraded to Windows 2000 Server ans SQL2000. This is fine > and > > > the > > > > > SQL Server is running. > > > > > I have changed the connection string in the VBapp to connect to the > > new > > > > > server, but the application will not run. The error being generated > by > > > VB6 > > > > > is on the connection open line, and just gives > > > > > "Client is unable to establish connection" > > > > > The Windows2000 server is available on the network. > > > > > Do I need an upgraded driver?? > > > > > Any help gratefully received > > > > > Thanks
Sat, 28 Jun 2003 23:05:41 GMT

Darren Gree #7 / 8	Upgrading connection to SQL Server 2000 from vb6 Quote: >The connection string is >driver=SQL Server;server=Global2ksvr;database=ni >Connecting using windows log-ons. >Works fine for old server Global, but not to new one. Try adding Truested_Connection=Yes. SQL 2000 client bits does not assume in the same way as 7.0 did. -- Darren Green SQL/DTS - http://www.swynk.com/friends/green/
Sun, 29 Jun 2003 03:29:24 GMT

chulc.. #8 / 8	Upgrading connection to SQL Server 2000 from vb6 Quote: > I have avb6 application running on Windows NT connecting to SQL Server 7, > and all is fine. > We have upgraded to Windows 2000 Server ans SQL2000. This is fine and the > SQL Server is running. > I have changed the connection string in the VBapp to connect to the new > server, but the application will not run. The error being generated by VB6 > is on the connection open line, and just gives > "Client is unable to establish connection" > The Windows2000 server is available on the network. > Do I need an upgraded driver?? > Any help gratefully received > Thanks This is the answer, maybe not the best but IT WORKS!!! I had same problem and now is fixed. Background info Microsoft have provided an upgrade to the odbc driver for clients on the sql server 2000 cd. This must be run on the COMPUTERS RUNNING YOUR PROGRAM. Look at their faq at http://support.microsoft.com/support/kb/articles/Q260/8/17.ASP To find out the before and after driver number go into control panel/odbc/drivers and look at the version no for sql server. It will be something like 3.70.08.20 Run the update below and check again. It will change to 3.2000. something. Solution Put in SQL server CD into each client machine (or run this file over network) on cd drive run file sqlredis below A copy of Sqlredis.exe is included on the SQL Server 2000 CD in the \MSEQ\x86\odbc folder. when you run it you will get no forms or other info but for a short second you will see it say it is updating control panel. Wait of couple of minutes then upgrade is complete. Run your program, good luck. Cliff Hulcoop If you liked this why not go to http://www.chulcoop.btinternet.co.uk Remember : Everyone needs help so if you can, do. Sent via Deja.com http://www.deja.com/
Fri, 11 Jul 2003 01:36:50 GMT

Page 1 of 1

[ 8 post ]