I previously used ODBC Manager (32 bit) to great success importing data directly from Filemaker Server to JMP. I recently upgraded to Catalina (MacOS 10.15.5) and knew that one of the casualties would be this ODBC utility. I downloaded the 64 bit ODBC manager from Actual Technologies and successfully installed it but get the following message when trying to open an FM database from within the ODBC interface in JMP:
dlopen(/Library/ODBC/FileMaker ODBC.bundle/Contents/MacOS/fmodbc.so, 6): image not found
I have navigated to Actual Technologies' web site believing I should download an ODBC driver but this comes at a hefty price tag, especially when converted to my local currency. Given the increasing costs of maintenance contracts and SSL certificates I had hoped to avoid further expenditure. Do I really need this and is there an alternative?
Apologies if I've put this in the wrong place.
My Filemaker solution uses a FM database and an ODBC connection to a MySql database that is used to serve data to a website.
I have complete read/write access to the data in the MySql database from inside FM and thus control of data published on the site.
I would like the MySql database to be able to access tables in the FM database in the same manner.
I have set up an FM ODBC connection to our FM server and that is visible in my local ODBC Manager, have tested the connection and that is good, but I can't see any way in the MySql apps I have installed on my system to create a table in the MySql database using live FM data, in the same way that I can make a table in FM using live data from the MySql database.
Is it possible to do this?
My main MySQL app is SequelPro. And occasionally MySQL workbench and associated tools.
I have been attempting to connect to a SQL database on my network using Monkeybread Software and each time that I attempt to do it I have encountered the same error, which I have attached here. I have set up an ODBC connection as well as made sure that I had the names correct, however I have gotten the same error message each time. Thank you for your help.
For about 12 years, we've had a FileMaker database import external data from a .mdb (Access) database that has data that is downloaded from some equipment. The process has survived several computer upgrades (Windows XP and Windows 7) and FileMaker version upgrades (created in 7 and currently running in 16). It broke when we moved into the Windows 10 environment. The script is set up to retrieve the data from the .mdb file and it says it can't access the file. So when I dive into the script and try to specify the ODBC connection it now asks for a username and password. We've never had a user name or password tied to either the .mdb file, the ODBC connection, or the FileMaker file. But no matter what we try, we can't get past this step. Is this a bug? What am I missing here?
Thanks in advance.
On windows 7 (VMware on OSX), using FMP17 and Microsoft Access 2016
Trying to do a ODBC import and selecting the datasource, I get asked for Username and password, even if the Access DB is not password protected.
The data sources are correct (tested from Livecode) and should be working without user name and password.
On the properties of the ODBC pane setup the path seems correct (not pointing to 32): %windir%\SysWOW64\odbcad32.exe
What am I missing?
Who Viewed the Topic