CodePudding user response:
Add:After found connected not SQL Server 2000, installed sqlncli _x64 (2008 edition), still can't connect!
2: XE do not use sqlncli, because I haven't installed 10.2, SQL Server can connect all the same, why help said we should install sqlcli???????
CodePudding user response:
SQL Server 2000 on the Server? The server is 10 years,CodePudding user response:
Can't ah, have a old program recently to upgrade, but the database customers don't buy, we have to use the old!!!!!!Also, just observe and FireDAC connect to the database is a default drive order, see below:
================================
The Connection definition parameters
================================
DriverID=MSSQL
Pooled=False
================================
FireDAC info
================================
Tool=RAD Studio 10.2
FireDAC=16.0.0 (Build 88974)
Platform=Windows 32 bit
Defines=FireDAC_NOLOCALE_META; FireDAC_MONITOR
================================
The Client info
================================
Loading driver MSSQL...
Loading odbc32. DLL driver manager
Creating the ODBC environment handle
The Searching for ODBC driver...
Checking for ODBC driver [11.0] SQL SERVER NATIVE CLIENT...
Checking for ODBC driver for SQL SERVER] [ODBC driver 11...
Checking for ODBC driver [10.0] SQL SERVER NATIVE CLIENT...
Checking for ODBC driver/SQL NATIVE CLIENT...
Checking for ODBC driver/SQL SERVER...
The Found (SQL Server)
================================
The Session info
================================
Failed to connect to the DBMS.
[FireDAC] [Comp] [Clnt] - 506. The Connection (Unnamed) establishment is canceled
CodePudding user response:
You can use 10.2 even, with 10.2 is not good, why must be the latest version?CodePudding user response:
Keep pace with The Times, Update 1 BUG fixesCodePudding user response: