Board index » delphi » ADO after Windows 2000 server service pack 3 upgrade

ADO after Windows 2000 server service pack 3 upgrade


2003-08-25 10:17:26 PM
delphi198
Hi,
We have a Delphi 5 application that connects to a SQL server 2000 database
on a Windows 2000 server machine. After we have installed the Windows 2000
service pack 3 the application just refuses to connect to the database. Can
this be due to a upgrade to ADO or does anybody have any idea what could
have caused this. We have also tried the normal change from Named Pipes to
TCPIP connection but this also didnt do the trick as it normally does.
Pls help
Rgds
Christo Botha
 
 

Re:ADO after Windows 2000 server service pack 3 upgrade

Check out the ADO installation by creating an UDL file with the connection
settings you use in the application.
If "Test Connections" succeeds the problem is most probably not in ADO.
You can also download the "comchecker" utility from the Microsoft DATA
website, it will tell you if anything is wrong with your ADO/OleDB/ODBC
configuration.
Danny
---
"Christo Botha" <XXXX@XXXXX.COM>schreef in bericht
Quote
Hi,

We have a Delphi 5 application that connects to a SQL server 2000 database
on a Windows 2000 server machine. After we have installed the Windows 2000
service pack 3 the application just refuses to connect to the database.
Can
this be due to a upgrade to ADO or does anybody have any idea what could
have caused this. We have also tried the normal change from Named Pipes to
TCPIP connection but this also didnt do the trick as it normally does.

Pls help

Rgds
Christo Botha



 

Re:ADO after Windows 2000 server service pack 3 upgrade

What sort of error message?
Perhaps it is a permission problem. Possibly the service pack set more
stringent permissions for access to the database.
"Christo Botha" <XXXX@XXXXX.COM>writes
Quote
Hi,

We have a Delphi 5 application that connects to a SQL server 2000 database
on a Windows 2000 server machine. After we have installed the Windows 2000
service pack 3 the application just refuses to connect to the database.
Can
this be due to a upgrade to ADO or does anybody have any idea what could
have caused this. We have also tried the normal change from Named Pipes to
TCPIP connection but this also didnt do the trick as it normally does.

Pls help

Rgds
Christo Botha