With an odbc connection, there is no problem
Does anyone know?
CodePudding user response:
Database field is the best text Nvarchar NtextCodePudding user response:
It is better to type nvarchar of many different languagesCodePudding user response:
Database field has been changed to nvarchar types, using odbc is no problem, use the oledb is no, I don't know how to return a responsibilityCodePudding user response:
You try try to turn off automatic character conversion, red font partThe SQLCA. DBMS="OLE DB"
The SQLCA. LogPass="password"
The SQLCA. LogId="sa"
The SQLCA. The AutoCommit=False
='SQLOLEDB' SQLCA. DBParm="PROVIDER and DATASOURCE='127.0.0.1', CommitOnDisconnect='no', PROVIDERSTRING='database=database name; AutoTranslate=no ', DBTextLimit='8000'
"
CodePudding user response:
Tried, still won't doCodePudding user response:
No one know?CodePudding user response:
With q, found in the user name today?Has been replaced by???
CodePudding user response:
In the SQLCA. DBParm join DisableBind=0