🚀 go-pugleaf

Native OLEDB provider is named SQLOLEDB in connection string, "or Microsoft 
OLEDB provider for SQL Server" in dialogs.

OLEDB provider for ODBC source is no longer supported by Microsoft. 
Microsoft OLEDB provider for SQL Server is much better for connection to MS 
SQL Server, using ADO with ODBC is quite buggy and has less features than 
using native providers. I do not see problem to use it instead of ODBC if 
you do not required to use DSN. I do not understand what you mean 
"re-configure connections", native provider can be configured to connect to 
any MS SQL Server.

//------------------------------------------
Regards,
Vassiliev V. V.
http://www.managed-vcl.com - using .Net objects in Delphi for Win32 + 
ADO.Net
http://www.oledbdirect.com - The fastest way to access MS SQL Server,
MS Jet (Access) and Interbase (through OLEDB)

"Glenn" <glenn.lucas@bowebellhowell.com> �������/�������� � �������� 
���������: news:42caf8c2$1@newsgroups.borland.com...
>
>
> Unfortunately, I have to use the ODBC connection with C++Builder5.  The 
> customer wants to re-configure connections.
> Is that not going to work?
>
> Thanks,
> Glenn
>
>
> "Viatcheslav V. Vassiliev" <support@oledbdirect.com> wrote:
>>Use native OLEDB provider for MS SQL Server, not OLEDB provider for ODBC
>>sources. Connection string is:
>>
>>Provider=SQLOLEDB;Data Source=<ServerName>;Integrated 
>>Security=SSPI;Initial
>>Catalog=<databse>;
>>
>>it is for Windows authentication. For SQL Server authentication, use User
>>ID=<User>;Password=<password>; instead of Integrated Security.
>>
>>//------------------------------------------
>>Regards,
>>Vassiliev V. V.
>>http://www.managed-vcl.com - using .Net objects in Delphi for Win32 +
>>ADO.Net
>>http://www.oledbdirect.com - The fastest way to access MS SQL Server,
>>MS Jet (Access) and Interbase (through OLEDB)
>>
>>"Glenn" <glenn.lucas@bowebellhowell.com> �������/�������� � ��������
>>���������: news:42caf1b6$1@newsgroups.borland.com...
>>>
>>> I am using an ADO Stored Proc component to connect with a SQL Server
>>> Stored Procedure.  The Stored Procedure uses 12 parameters - 7 inputs 
>>> and
>>> 5 outputs.  The variable types are integers, strings, and DateTimes.
>>>
>>> The problem is when I attempt to set the "Active" flag to "true"
>>> (either in the Editor or Programmatically), an error popup
>>> appears with the message:
>>>
>>> [Microsoft][ODBC SQL Server Driver]Optional feature not
>>> implemented
>>>
>>> Can someone tell me how I find out what "optional feature" it
>>> is talking about?
>>>
>>> Thanks.
>>
>>
>