My agency has upgraded from Windows XP clients to Windows 7 64-bit clients. They also upgraded the SQL server from SQL 2005 Express to SQL 2012.
They have a Visual Basic 6 application that successfully connects to the SQL 2005 express server from a Windows XP machine using the 2005 SQL Native client. My task is to successfully connect VB application from the 64-bit Windows machines to SQL Server 2012. I am using the SQL Server 2012 native client.
I have created a .udl file to ensure I am using the correct connection string. I have copied that string several time and several different ways and I continue to receive the following errors:
"Invalid connection string attribute"
"Cannot create database source recordset"
"Login failed for user ' '. The user is not associated with a trusted SQL server connection".
The application populates the information from a .ini files that reads:
SERVER=ServerName
DATABASE=Database Name
ISSQL=True
DBFILE=
PROVIDER=SQLNCLI11.1
(I would like to tweak the .ini file instead of messing with the VB application)
According to the .udl files the connection string should look something like this:
[oledb]
; Everything after this line is an OLE DB initstring
Provider=SQLNCLI11.1;Integrated Security=SSPI;Persist Security Info=False;User ID="";Initial Catalog=Reliant;Data Source=ARCWS4;Initial File Name="";Server SPN=""
I have also look at
www.connectionstring.com and I still cannot get the correct parameters. I still receive the errors mentioned above.
I have attached the Visual Basic class that creates the connection string.
I have checked the SQL server and compared the old with the new server parameters and cannot seem to find any differences. Everything seems to be in order.
Any help would be appreciated
clsData.txt