External Datasource mySql

Hi u can use odbc connection to connect to the mysql and filll the records.

You can only store data in mysql, you still need the application file to be stored somewhere: on your workstation or on a server depending on wheter you share these data or not.
Using mysql as the main storage for filemaker has some drawbacks, the main one being that filemaker never knows if someone has added/updates data since you loaded records, and you then have to refresh your data manually to make sure it is still true, so see it mainly to recuperate data from other databases, or read partial information to be related it to something else rather than being the main storage. But it remains very handy for import/export.
How does it work: from the workstation you need to create a ODBC source to mysql db using the mysql odbc driver. if suing a fm server, this link can be made at the server level, but you need the fm server 'advanced', more expensive...

Hi,

Here u can find how to configure the odbc connection to connect to mysql

http://dev.mysql.com/doc/refman/5.0/en/connector-odbc-configuration-dsn-windows.html

U can download odbc at http://dev.mysql.com/downloads/connector/odbc/5.1.html 

U can choose the option depending on ur requirement

For the last year under Filemaker 9 I have supported live connections to MSSQL from filemaker and have not had any problems seeing immediate updates to SQL and I have been updating the tables from filemaker where appropriate. In order to do updates you have to be aware of the underlying procedure that resides under the field.

Please advise if you would like to see and example I can set up a webex to show you

interesting... I once did a common data source for a php app + fm connected to mysql, and there was no way to let fm to find modifications done by php unless reloading the foundset.
what do you call an "underlying procedure"?? I finally used servoy for both, since it has a decent web client.
though I am not the asker, I am interested to know how you made it transparent.

All I do is set up the MSSQL odbc service on the computer I am connecting from or at the server then I add the MSSQL table to the relationship page and relate it to a local table . In most cases a table with a global used as a key and the data that is linked is always current. I can also write to the table with the appropriate SQL command. If there are underlying procedures set in SQL for example lets say you try to write to an autoenter field the SQL command will not allow you to write to that field.  If you are not aware of the field setup on the SQL side you may get the impression that you can't write to the SQL fields from Filemaker, when in fact you can...I do it all the time

I don't know how it works in MySQL but in MSSQL we get instant updates...We don't write using FM functions instead when it is time to write to the external database we execute a SQL command from inside FM that acts on the external table.

I will try what you suggest when I get a chance and see what happens...

what's the reason to write using SQL queries rather than using it the strait way? different MSSQL behaviour? or using converted fm6 stuff?

I have not tried the other, we are in the drug manufacturing business and there are many design reasons why we use SQL commands that are intended to limit how data is replaced or changed. For our application flow it is a better approach. If you are not complying with FDA guidelines I think you can do either. I have never tried the other.... If you remember is some of our prior banters, that we write data to a global , authenticate the user and then copy it to a table and write and audit record.

I don't remember all of it, but I do remember the temp step before enabling data in (which I also do for major info, to create new records sometimes) and the extensive audit you have to do.
Actually new data checking would be much easier if fm would allow to display/type in variables.