Problem description: I am using Libre Office Version: 4.3.4.1 on my Mac OSX 10.10 Yosemite. In Base Database, I would like to connect MS-SQL server using unixODBC DSN. But it seems the Libre Office tries to connect via iODBC, not unixODBC. (I never installed iODBC on my Mac.) Steps to reproduce: 1. Following the below link, I already setup unixODBC, FreeTDS using Homebrew and all the tsql/isql connection tests were fine. http://www.joecjr.com/2014/07/27/install-and-use-freetds-unixodbc-and-rodbc-or-pyodbc/ 2. After installing, I launched "Database Wizard" from Base database. And choose 'ODBC' from "Connect to an existing database", I entered s01, my unixODBC DSN name, to "Name of the ODBC data source on your system" field. (When I clicked 'Browse' no registered data source were shown.) And I typed my unixODBC username and checked Password required. 3. When I clicked 'Test Connection' button and input the password, an error occurred as below. [iODBC][Driver Manager]Data source name not found and no default driver specified. Driver could not be loaded. Current behavior: SQL Status: IM002 [iODBC][Driver Manager]Data source name not found and no default driver specified. Driver could not be loaded Expected behavior: Establishing an ODBC connection using unixODBC.
The ODBCAdmin tool and corresponding iodbc libraries are no longer present by default, but can still be installed, either from Apple, or now, a more recent app bundle called ODBC_Manager, have you tried that instead of unixODBC ? It could well be that the LO production build is made with the libraries from the ODBCAdmin tool (system dev libs) and therefore not unixODBC dev libs
As a cvomparison, I use ODBC Manager, MySQL odbc driver 5.3 and LO 4332 on OSX 10.10 and it works.
Setting to needinfo as unixodbc is not required for odbc access, when OS-native solution exists. Please test with "ODBC Manager.app" and report back
Adding self to CC if not already on
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.