I am writing a front end in Access that connects to SQL Server. I am using the default {SQL Server} driver since some of the computers/laptops/tablets that will be using it probably will not have a driver installed for SQL Server. The FE opens fine on my computer as one would expect, and will open on another computer (that does not have any driver's installed), but when attempting to open the FE on 2 other machines, both get stuck at the ACCESS splash screen. I have checked Task Manager and the Microsoft Access (32-bit) background process is running. All of our machines are 64-bit. Can anyone help with this?
I've researched trying to find a different default driver for SQL Server but have come up empty handed. Installing a driver like {ODBC Driver 18 for SQL Server} isn't feasible since it would entail having our outsourced IT company install it and charging us for it.
Follow up: It is the Microsoft Access splash screen that is locking up (the one that appears whenever you open Access), not a custom one. And I am not deploying the DB, simply sending it in an email for the user to copy to their computer. I am using Autoexec to run my Main function to connect to the backend server. The VBA to connect is:
Public curDB as ADODB.Recordset: Set curDB = New ADODB.Connection
conString = "Driver={SQL Server};Server=HL-XXX;Database=PalletQuoting;UID=XXXX;PWD=XXXX;Encrypt=NO"```
You don't mention where the SQL Server is located. However if the SQL instance is not on your computer.
Above being the case? Then the application should work just fine from all computers on that same network.
Just make sure WHEN you link the table(s), make sure you using FILE DSN, and not a user/system DSN. The reason for this is then you don't require any setup on each workstation by using the standard SQL driver as you noted.
So, when you link the table, don't use system or user DSN, but make sure you linked the tables using a FILE DSN. By using a FILE DSN, then no setup is required on each workstation.
So, with above, then do the linked tables work and open just fine, or is it just the custom ADO code you have that fails?
I would suggest you ensure the linked tables work first before you start working on the VBA + ADO code you have.