Search results
16 cze 2021 · I get a runtime error 3709 when trying to connect via VBA to a SQL Server using Windows authentication. The problem occurs on this line: .ActiveConnection = conn. Here is the complete code used to connect: Dim strConn As String. Dim wsReport As Worksheet. Dim col As Integer. strConn = "Provider=SQLOLEDB;"
26 cze 2015 · The ADO connection object has an Errors collection, which you can check after running your SQL: conn.Errors.Clear Set rs = conn.Execute(Myquery)
21 wrz 2023 · The following articles provide details for various tools and procedures to troubleshoot different connectivity errors: Configure firewalls to work with SQL Server. Describes how to configure Windows firewall for successful connections to instances. Test connections to SQL Server by using Universal Data Link (UDL) files
20 sty 2022 · I am using VBA to try and connect to SQL server. Here is the code: Sub GetDataFromADO () 'Declare variables' Set mConn = New ADODB.Connection. Set mRS = New ADODB.Recordset. Dim strSQL As String. 'Open Connection'
27 mar 2024 · If the connection is closed after the ClientHello, check if there's a TLS 1.0 or TLS 1.2 mismatch between the client and server. If they're the same, check the enabled cipher suites and enabled hashes on both machines.
21 mar 2011 · Solution. There could be several reasons you get these error messages. Follow the below steps to see if you can resolve the issue. Step 1 - Check that you can ping the SQL Server box. Make sure you are able to ping the physical server where SQL Server is installed from the client machine.
19 sie 2021 · I have always been successful in connecting my VBA solutions in MS Access as a client to my company’s SQL Server, but I struggled for a long time to figure out how to connect to a SQL Server Express LocalDB instance on my personal computer until now.
