This topic is 2559 days old. Please don't post here. Open a new topic instead.
How to Build FileMaker Web Apps for High Traffic using MySQL Backend and 360Works MirrorSync
Why Sync FileMaker and MySQL?
FileMaker is the best tool for rapid application development, but it is not the most reliable or scalable option for high traffic web sites. MySQL provides that reliability and scalability, but can't compare to FileMaker for development productivity and user friendliness.
360Works MirrorSync bridges this gap, letting you use each tool for its best purpose. Quickly create layouts, scripts, and schema in FileMaker Pro, test and refine them, then use MirrorSync to publish all your record data to MySQL and keep both databases in sync moving forward. You can use industry-standard tools and frameworks (or hire from a vast talent pool) to create highly reliable and scalable web apps.
In the event that FileMaker Server is down or rebooted for any reason (such as software upgrades), your MySQL web app will continue running and serving users. MirrorSync will detect when FileMaker Server comes back online and bring both databases back in sync.
This video, narrated by Junior Perez of 360Works, takes you on a step-by-step walk-through of how to sync between FileMaker Server and MySQL. Junior demonstrates how to start with a completely empty MySQL Server, create the database and tables, and set up an auto-scheduled sync to run every 60 seconds. The process is the same for any other JDBC-compatible database such as SQL Server, Oracle, or PostgreSQL. The license price for syncing one FileMaker Server with any one of these databases is $1,800, with discounts available for educational and non-profit organizations.
If you would like to involve 360Works in configuring your sync, or in creating a web application backed by MySQL, please contact us for consulting and development assistance.
Read More on MirrorSync or Download Now!
360Works MirrorSync Stay updated with 360Works
By Richard Carlton
In this Livestream, we're discussing containers! Discover the different ways to optimize your external container data storage on the server side, as well as how to do a "split" container data setup! Future live streams: https://fmtraining.tv/#LIVE
360Works 25 Year Anniversary and New Portfolio Offer
We are celebrating 25 years in business! Thank you for your support. If you are using a FileMaker plug-in or two from 360Works, we encourage you to try the 360Works Portfolio Bundle to receive all products.
Now through next week enjoy a 25% off sale on our Portfolio Bundle!
You already receive 75% off the entire suite of plug-ins with the Portfolio Bundle deal being offered at $1,995, and with our 25th Anniversary Offer you get an additional 25% off, making your final cost only $1,496.25!
Use code: 360is25 at checkout. (Online orders only, discounts cannot be combined, new portfolio)
This offer is for new Portfolio Bundle purchases only and will be on now, through next week, ending Friday, April 9, 2021.
Already own a product or two from 360Works? You can apply your licenses to receive credit for select products upon checkout of the Portfolio Bundle.
New Website Design
Have you noticed the new look of our website? Be sure to stop by and take a look: https://www.360works.com/products/
New Product Updates
We recently released a new major version of the 360Works Email Plugin, to include OAuth support for Gmail and Office 365. Additionally, we released a new major version of our FileMaker Server offsite backup, 360Works SafetyNet, with improvements for increased safety, reliability, speed, ease of management and lower cost.
Case Study: MirrorSync in Africa for Promasidor
Learn how FileMaker synchronization happens across the continent of Africa using 360Works MirrorSync in a solution for Promasidor Food and Beverage with experience shared from Technology Professional, Serge De Pauw at Promasidor. Read the story.
We are relatively new to MirrorSync (6.12). We can have a system which is syncing with no issues. We create a new record on the FMS in a table that is synced to the Spoke (iPad). After the iPad syncs and receives the new record, the next time the iPad tries to sync, they receive an error that there is a Duplicate ID...
On researching the issue, whenever we create a single record on the Hub, 2 records with the same ID are created on the Spoke with the same ID.
This effectively breaks the sync and needs remediation by the user of the iPad by the deletion of one of the records.
I can sense the eye rolls but, I’ve just upgraded to FMS19 on a MacPro after upgrading it to Big Sur and the database container fields are reporting missing files. I have defined the alternate database folder and its associated external storage volume which was verified. Could I have the syntax wrong? I have “filemac:/System/Volumes/External Data/Container Data/“.
“External Data” is the name of my external drive. The “Volumes” folder is of course hidden but would that matter? I’ve tried unhiding it, but to no avail.
Should one use “%20” in lieu of spaces? Should one use the sub folder “Container Data” in the path, or is that assumed anyway?
I’ve tried these permutations but am getting nowhere. Does one need a restart after specifying the external container path - it didn’t seem to suggest so?
Who Viewed the Topic