Tried adding an ODBC source using both MySQL 8.0.22 and MariaDB 3.1.10 drivers in Unicode mode and I can connect just fine, however it's impossible to add a table onto the relationships graph. It sees the table's name but when I try to add it, I get
This action cannot be performed because the required table is missing. error. It works fine with ANSI version of the MySQL driver, sans the ability to work with Unicode of course. I've tried multiple combinations, including making the database and the table strictly "latin", it still refuses to add the table. The test database itself is very simple, just a single table and a single field, no spaces and no unicode characters in names. Test/test/test, basically, tested with an empty FM database. The server is running MariaDB 10.4.16. Any pointers to solve that?
By David Simpson
Fremont, California - .com Solutions Inc. today is pleased to announce the release of FmPro Migrator Platinum Edition 9.13 with support for automated Microsoft Access to FileMaker Pro 19 migrations. FmPro Migrator Platinum Edition 9.13 enhances the Access to FileMaker 19 conversion feature in the following ways:
* Relationships are created more accurately during the conversion process because all table/fields are now converted to be SQL compliant.
* Table occurrences are also standardized to use SQL compliant table/field names so that they get created correctly. The menu allowing manual selection of a TO base table now displays the converted base table names.
* The list of TOs displayed on the Layouts tab now uses the converted TO names when updating layout TO names manually.
* When performing an Access to FileMaker data transfer, the completion status now displays correctly after it has completed.
* On macOS and Windows support has been added for creating layouts with FileMaker Pro 19.1.2 by changing the process which deletes layout parts before pasting the layout contents via the clipboard.
Converting legacy Microsoft Access databases to FileMaker 16 offers many advantages including:
* Cross platform compatibility: FileMaker solutions run directly on macOS, Windows and IOS devices. WebDirect serves FileMaker custom apps to all mobile and desktop platforms running a supported web browser. Access can only run on the Microsoft Windows operating system.
* Easier database sharing: FileMaker database files can be shared using FileMaker Server or FileMaker Cloud with macOS, Windows and IOS devices. WebDirect serves FileMaker database files to any device or platform using any supported web browser.
* Improved reliability: Access database files require frequent maintenance to "compact and repair" the database. Sharing Access files on a network file share typically results in file corruption. FileMaker solutions don't have any of these problems and file sharing is reliably supported from within the FileMaker application for peer to peer sharing or via FileMaker Server or FileMaker Cloud on AWS.
* Greatly enhanced file capacity: FileMaker supports a 7TB filesize compared with the anemic 2GB Access filesize limit. If the Access database file ever exceeds the 2GB file size limit, it will immediately become corrupted.
* Easier Development: Upgrading to FileMaker Pro 19 also offers developers the opportunity to take advantage of the latest design, development and security features included with FileMaker Pro 19 and FileMaker Server 19 and FileMaker Cloud including WebDirect capacity enhancements.
FmPro Migrator Platinum Edition 9.13
Access to FileMaker Migration Feature
Download FmPro Migrator
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.
Who Viewed the Topic