I started this thread in the Office for Mac forum (without solution), but was advised by the moderator to try to post here. I am trying to get Excel 2016 (15.30, Office 365 subscription) to acces a filemaker database via ODBC, as a client. The database seems to communicate via ODBC and iQueryODBC can see the tables and data in the Filemaker Database. When I try to establish a link between Excel and Filemaker via ODBC (Data / Get External Data / From Database) the iODBC chooser window opens but with no functionality - DSN connections cannot be tested (nothing happens) or configured, and clicking OK to advance to Query just brings me back to the Spreadsheet, with no data. I suspect there is some confusion with the versions of the iODBC chooser that Excel is calling up, but I do not see how I can check to see that its 64 bit and, if its not, how I can force Excel to use a different Data Source Chooser that is 64 bit. Any ideas very much appreciated.

*Panda Security Monthly price (starting at). All plans are available for 1, 3, 5, 10, and an unlimited number of devices. **VPN PREMIUM: Available for 5 Windows and Android devices. Unlimited devices: Subject to limitations on reasonable home use and purpose of the product. Unlimited license registration for one customer in one household only. Antivirus protection adapted for every home Remember: You and your private information are in the crosshairs of cyber criminals. Protect all your Windows, Mac, Android and iOS devices from ransomware, cyber espionage and targeted attacks.

May 31, 2012 - You probably just need to install the full iODBC SDK, which includes the iODBC Frameworks against which Microsoft Excel and its helper. INTO Syntax, and then open the CSV file in Excel. This doesn’t give a “live” data connection — if the data in your database changes, you’d have to re-export it to CSV and re-import to Excel every time. But it’s the only solution that works without additional third-party software.

Hi, >>I suspect there is some confusion with the versions of the iODBC chooser that Excel is calling up Sorry but my knowledge about iODBC chooser is limited and we currently do not have the environment to help you test this. However, have you tried referring to the instructions into see if we can verify its bit version using file command? Besides, a new (Version: 15.31.0, Build 17021600) has been released on February 16, 2017. It is recommended to try checking for and installing the latest updates to see if there will be any improvement. Hope this can be helpful. Best regards, Yuki Sun Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact.

List: From: Chris Ridd Date: March 18 2005 7:09pm Subject: Re: mac / excel / odbc On 18/3/05 11:27 am, Daniel Griffiths wrote: > I am having trouble getting the mysql mac ODBC connector to work in > excel for OS X. Works fine under windows but mac excel doesnt list it > at all. > > the connector is installed fine and i have set up the dsn and tested > the connection and thats ok its just that excel can seem to find it. > > do i need a special connector for excel? I haven't tried with Excel 2004, but Excel v.X required a CFM bridge, because although the OS's ODBC driver is a Mach-O library, and the MyODBC driver is a Mach-O library, Excel is not a Mach-O application. (Mach-O and CFM are different kinds of executable format.

CFM is deprecated by Apple.) If you google a bit on the subject, you ought to find a good article at www.macdevcenter.com about this, which should link to www.openlinksw.com who have the CFM bridge. > The contents of this e-mail (including any files transmitted with it) are > confidential to the ordinary user of the e-mail address to which it was > addressed and may also be privileged. It may be read, copied and used only by > the intended recipient. > It is not to be relied upon by any person other than the addressee except with > our prior written approval.

If no such approval is given, we will not accept > any liability (in negligence or otherwise) arising from any third party > acting, or refraining from acting, on such information. > If you receive this message in error, please immediately delete it, destroy > all copies of it and notify the sender. You must not use or disclose any part > of this message if you are not the intended recipient. We may monitor all > E-mail communication through our networks. > If you contact us by E-mail, we may store your name and address to facilitate > communication. > Any views expressed in this message are those of the individual sender, except > where the message states otherwise. > We take reasonable precautions to ensure our E-mails are virus free, however, > we cannot accept responsibility for any virus transmitted by us and recommend > that you subject any incoming E-mail to your own virus checking > procedures.Thank you.