ODBC Drivers for End Users

[CPGDeveloper]

Hi All~

So I have an Access Application that is using Azure SQL Server as a Back End. I'm connecting through an ODBC Driver that none of the end users have currently. As far as I understand, every end user would need this driver installed on their individual machines. Is that true? Is there any way around this?

I currently have a batch scripts that updates the front end on everyone's desktops every time I update the application -- maybe I can include the appropriate .dll driver files when I do this and place them in the correct directories? Or is it more complicated than that?

 

[xenou]

I think drivers need to be "installed". It may be possible to put more of the connection and actually data access in the back end... not sure (may be too late depending on your setup now). Good news is that you would only have to install the driver once.

 

[CPGDeveloper]

Hmmm....are you suggesting if I split the database, where the front end is linked to back end tables in another access database, but all the tables in the back end access database are linked to SQL? Would that mean the front end user would not need the odbc driver?

We could just install the driver on the server where the back end resides?

 

[xenou]

That might be possible. How many users do you have?

 

[CPGDeveloper]

That might be possible. How many users do you have?

At the moment, no more than 20, but we are getting push back from the powers that be about installing odbc drivers for everyone. So I was looking for a way around it.