We use Access 2003 with a 2000 format database as the front end for a number of linked tables to SQL Server 2000. We recently added SSL encryption to the SQL Server for another project. Using the Server Network Utility I've confirmed that Protocol Encryption is checked. However, the web server ASP.NET connection string did not require any changes when connecting to this database server. Specifically, we did not add Encrypt=YES to the connection string but our app still connects to the database server.
The Access database is separate from the .NET app and resides on the database server. It uses a DSN for all of it's linked tables. It did not require any changes eiher once we enabled the encrypted protocol.
Since the protocol encryption, we have begun to get 3146 ODBC Call Failed errors. The code below is called when a user moves between records on a form and causes the error when the OpenRecordset method is called. The Connect string is as follows:
icrosoft Office 2003;WSID=MyServer;DATABAS
The OpenRecordset call is made whenever the user changes records but the error doesn't always happen. I'm interested in the following:
1) Is the database server actually forcing protocol encryption?
2) What do I need to do to fix the access database so it stops causing errors?
Thank you in advance for your help.
strSql = "SELECT dbo.uMyFunction(" & _
nID & ", " & _
dValue1 & ", " & _
dValue2 & ", " & _
0 & ")"
Set db = CurrentDb
Set qdf = db.CreateQueryDef("", strSql)
qdf.Connect = CurrentDb.TableDefs("dbo_ClientUser").Connect
Set rs = qdf.OpenRecordset