AnsweredAssumed Answered

ODBC with Mysql and Global Fields

Question asked by user22756 on Jun 22, 2014
Latest reply on Jun 22, 2014 by wimdecorte

I'm about to begin to develop a website (PHP - MySQL) that will be monitored and followed from within FM13.

I've got my ODBC running very smoothly into Filemaker. I can create TO's based on the MySQL-tables, use them in layouts, etc...

But I'm wondering what is best practice on this kind of stuff.

For instance:

Usually, when a FM-user wants to search for a records, for instance, I have a global field in my table, to perform a "Live-Search".

How is this done with a MySQL-table as resource?


Our MySQL user for the ODBC has no delete permits. Removing something is usually done by setting a flag to 0. This is because we try to avoid a user to delete records as easy as it gets in FM. Do you also use the MySQL table as a live resource, or do you sync with a local table, by script, so you can avoid accidentally deleted records?

It's just an example, but I'm wondering how you do this?

I'm rather new to FM, but very eager to get into it further...