February 19, 2010 at 10:23 am
Hi,
I have changed my vb 6.0 apps so they can connect to SQL Server 2005.
I changed the provider from MDAC to SQLNCLI.
This is because i want to have full access to the new functionalities of SQL Server 2005.
What about VB.net ? people at the company use a connection string like this:
"Data Source=servername;Initial Catalog=databasename;Integrated Security=True"
Can they take full advantage of SQL Server 2005 new functionalitites? or they have to change anything like i did in vb 6.0?
Thank you.
P.S - They (developers) say that they are using the class "SQLClient" to connect.
February 19, 2010 at 10:40 am
I have changed my vb 6.0 apps so they can connect to SQL Server 2005.
I changed the provider from MDAC to SQLNCLI.
If I remember correctly SQLNCLI is a provider for unmanaged code like VB6 and VC++ and so VB.NET before .NET 3.5 does not use it. You should also know connection string and the provider are generally not related because I use the same connection string for SSRS,SSIS and .NET applications.
Kind regards,
Gift Peddie
February 19, 2010 at 10:45 am
sorry didn't understood very well your answer
February 19, 2010 at 11:12 am
river1 (2/19/2010)
sorry didn't understood very well your answer
What I am saying is SQL Native Client provider is for unmanaged code like VB6 and VC++, VB.NET 2.0 and below can use it but it was not defined for it but in VB.NET 3.5 and above it is defined so if you are using VB.NET 2.0 and below don't use SQL Native Client. Check the link below for more about SQL Native Client.
http://msdn.microsoft.com/en-us/library/ms188718.aspx
Kind regards,
Gift Peddie
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply